CVE-2026-3045
Received Received - Intake
Unauthorized Data Access in Simply Schedule Appointments Plugin

Publication date: 2026-03-13

Last updated on: 2026-03-13

Assigner: Wordfence

Description
The Appointment Booking Calendar — Simply Schedule Appointments plugin for WordPress is vulnerable to unauthorized access of sensitive data in all versions up to and including 1.6.9.29. This is due to two compounding weaknesses: (1) a non-user-bound `public_nonce` is exposed to unauthenticated users through the public `/wp-json/ssa/v1/embed-inner` REST endpoint, and (2) the `get_item()` method in `SSA_Settings_Api` relies on `nonce_permissions_check()` for authorization (which accepts the public nonce) but does not call `remove_unauthorized_settings_for_current_user()` to filter restricted fields. This makes it possible for unauthenticated attackers to access admin-only plugin settings including the administrator email, phone number, internal access tokens, notification configurations, and developer settings via the `/wp-json/ssa/v1/settings/{section}` endpoint. The exposure of appointment tokens also allows an attacker to modify or cancel appointments.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-13
Last Modified
2026-03-13
Generated
2026-05-06
AI Q&A
2026-03-13
EPSS Evaluated
2026-05-05
NVD
CVE-2026-3045
EUVD
EUVD-2026-11758
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
simply_schedule_appointments appointment_booking_calendar to 1.6.9.29 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-862 The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The Appointment Booking Calendar — Simply Schedule Appointments plugin for WordPress has a vulnerability that allows unauthorized users to access sensitive data. This happens because a public nonce (a security token) that is not tied to any user is exposed through a public REST endpoint. Additionally, the method responsible for retrieving settings relies on a permission check that accepts this public nonce but does not filter out restricted fields for unauthorized users.

As a result, unauthenticated attackers can access admin-only plugin settings such as the administrator's email, phone number, internal access tokens, notification configurations, and developer settings. They can also obtain appointment tokens, which can be used to modify or cancel appointments.


How can this vulnerability impact me? :

This vulnerability can lead to unauthorized disclosure of sensitive administrative information including contact details and internal tokens. Attackers can also manipulate appointment data by modifying or canceling appointments without authorization.

Such unauthorized access and manipulation can disrupt business operations, compromise user trust, and potentially lead to further exploitation if internal tokens are used to access other systems.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

I don't know


How can this vulnerability be detected on my network or system? Can you suggest some commands?

I don't know


What immediate steps should I take to mitigate this vulnerability?

I don't know


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart