Booked <= 2.2.5 - Missing Authorization on AJAX Actions
Strategic Overview
- Status
- Patched in 2.2.6
- Affected Plugin
- Booked - Appointment Booking for WordPress
- Affected Version
< 2.2.6- CVSS
- 8.8High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE pending
At a glance
This record tracks a high-severity Missing Authorization vulnerability in the Booked - Appointment Booking for WordPress WordPress plugin, affecting versions < 2.2.6. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 2.2.6; sites on affected versions should update now. Disclosed February 2020, reported by Noman Riffat.
Vulnerability Overview
The Booked plugin for WordPress is vulnerable to authorization bypass due to missing capability checks on several functions hooked via AJAX actions in versions up to, and including, 2.2.5. This makes it possible for authenticated attackers with subscriber-level permissions and above to execute several unauthorized actions.
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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
Reaching this weakness in Booked - Appointment Booking for WordPress < 2.2.6 takes a caller who can reach the endpoint. 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 Booked - Appointment Booking for WordPress the fix is 2.2.6: builds < 2.2.6 are affected, anything from 2.2.6 onward is not.
Remediation
Update to version 2.2.6, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Booked - Appointment Booking for WordPress 2.2.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Booked - Appointment Booking for WordPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C