Smart Appointment & Booking <= 1.0.8 - Missing Authorization to Unauthenticated Arbitrary Booking Cancellation
Strategic Overview
- Status
- Patched in 2.0.0
- Affected Plugin
- Smart Appointment & Booking
- Affected Version
<= 1.0.8- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-5693
At a glance
CVE-2026-5693 is a medium-severity Missing Authorization vulnerability in the Smart Appointment & Booking WordPress plugin, affecting versions <= 1.0.8. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.0.0; sites on affected versions should update now. Disclosed May 2026, reported by Itthidej Aramsri (Boeing777).
Vulnerability Overview
The Smart Appointment & Booking plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check and a nonce validation logic flaw in the saab_cancel_booking() function in all versions up to, and including, 1.0.8. The nonce check uses && (AND) instead of || (OR), which means providing any value for the security parameter causes the entire check to be skipped. This makes it possible for unauthenticated attackers to cancel arbitrary bookings by supplying a predictable booking ID.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Smart Appointment & Booking <= 1.0.8 carries this weakness at saab_cancel_booking(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Smart Appointment & Booking the fix is 2.0.0: builds <= 1.0.8 are affected, anything from 2.0.0 onward is not.
Remediation
Update to version 2.0.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: Smart Appointment & Booking 2.0.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Smart Appointment & Booking
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C