Bookster – WordPress Appointment Booking Plugin <= 1.1.0 - Unauthenticated Appointment Manipulation
Strategic Overview
- Status
- Patched in 1.2.0
- Affected Plugin
- Bookster – Appointment Booking Management System
- Affected Version
<= 1.1.0- CVSS
- 5.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2024-5071
At a glance
CVE-2024-5071 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the Bookster WordPress plugin, affecting versions <= 1.1.0. 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 1.2.0; sites on affected versions should update now. Disclosed June 2024, reported by Roshan Cheriyan.
Vulnerability Overview
The Bookster – WordPress Appointment Booking Plugin plugin for WordPress is vulnerable to unauthorized data manipulation in all versions up to, and including, 1.1.0. This is due to the plugin not properly validating the book_status parameter. This makes it possible for unauthenticated attackers to update their booking status to approved.
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-639: Authorization Bypass Through User-Controlled Key
Reaching this weakness in Bookster <= 1.1.0 takes no account at all. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For Bookster the fix is 1.2.0: builds <= 1.1.0 are affected, anything from 1.2.0 onward is not.
Remediation
Update to version 1.2.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: Bookster 1.2.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Bookster – Appointment Booking Management System
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C