Atomic Edge analysis of CVE-2026-16540: The Simply Schedule Appointments WordPress plugin before version 1.6.12.6 contains an unauthenticated Insecure Direct Object Reference (IDOR) vulnerability in its REST API. The flaw affects the appointment model endpoints for group cancellation, group deletion, and appointment purging. It carries a CVSS score of 5.3 (Medium) and maps to CWE-639. Unauthenticated attackers can invoke destructive operations on appointment data by supplying a valid identifier token that is not sufficient for the action being performed.
Root Cause: The vulnerability resides in the REST route registration within `includes/class-appointment-model.php`. The routes for `group_cancel`, `group_delete`, and `purge_appointments` (lines 1524, 1541, and 1558 in the vulnerable version) used `get_items_permissions_check` as their `permission_callback`. That callback is designed for listing items and accepts broad, weak access signals, including the global token and the public_read_access_token. These tokens prove only read-level or site-wide context, not ownership or management rights over a group or the whole table. The patch replaces the callback with dedicated permission checks. `purge_appointments_permissions_check` now requires the `ssa_manage_others_appointments` capability because `purge_appointments()` deletes across the entire appointments table. `group_cancel_permissions_check` and `group_delete_permissions_check` now call `get_item_permissions_check`, which enforces a manager capability or verified ownership of the group through the lead appointment. Atomic Edge analysis confirms that the vulnerable logic trusted a user-controlled key (an ID or token) without binding it to the requested operation or resource scope.
Exploitation: An unauthenticated attacker targets the WordPress REST API namespace used by the plugin. The attacker sends a POST request to `/wp-json/simply-schedule-appointments/v1/appointments/group/{id}/cancel` or `/wp-json/simply-schedule-appointments/v1/appointments/group/{id}/delete`, or a GET request to `/wp-json/simply-schedule-appointments/v1/appointments/purge`, and supplies the weak token as a parameter (for example `token=` or `id_token=`). Because the pre-patch permission callback accepts the global token or public_read_access_token, the request passes authorization. The `group_cancel` and `group_delete` handlers then act on the group identified by the route ID. The `purge_appointments` handler deletes appointments across the table based on scope parameters such as `purge_past_appointments`. The attacker needs no WordPress account and no valid nonce beyond whatever the weak token provides.
Patch Analysis: The patch introduces three dedicated permission callbacks in `includes/class-appointment-model.php`. `purge_appointments_permissions_check` returns `current_user_can( ‘ssa_manage_others_appointments’ )`, denying the global token and public_read_access_token entirely. The group callbacks delegate to `get_item_permissions_check`, which already supports a manager capability or ownership of the group via the lead appointment (staff assignment, customer account, or the lead appointment’s id_token). Before the patch, the group routes shared the broad item-listing check. After the patch, each route has a callback scoped to its actual impact. The version bump to 1.6.12.6 and the Elementor constant changes are unrelated packaging updates.
Impact: Successful exploitation lets an unauthenticated attacker cancel or delete appointment groups and purge appointments across the site. This causes loss of scheduling data, denial of service for booked customers, and disruption of business operations. The flaw does not expose data directly or lead to code execution. The confidentiality, integrity, and availability impact is limited to appointment records, which matches the 5.3 CVSS rating.







