WP Booking Calendar <= 10.10 - Unauthenticated Post-Confirmation Booking Manipulation
Strategic Overview
- Status
- Patched in 10.10.1
- Affected Plugin
- Booking Calendar
- Affected Version
<= 10.10- CVSS
- 5.3Medium
- Weakness type
- CWE-285 · Improper Authorization
- CVE
CVE-2024-13821
At a glance
CVE-2024-13821 is a medium-severity Improper Authorization vulnerability in the Booking Calendar WordPress plugin, affecting versions <= 10.10. 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 10.10.1; sites on affected versions should update now. Disclosed February 2025, reported by Asaf Mozes.
Vulnerability Overview
The WP Booking Calendar plugin for WordPress is vulnerable to Unauthenticated Post-Confirmation Booking Manipulation in all versions up to, and including, 10.10. This is due to the plugin not properly requiring re-verification after a booking has been made and a change is being attempted. This makes it possible for unauthenticated attackers to manipulate their confirmed bookings, even after they have been 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-285: Improper Authorization
Reaching this weakness in Booking Calendar <= 10.10 takes no account at all. Improper authorization means a permission check exists but does not cover the case being exercised, so a caller who is allowed to do one thing is allowed to do a neighbouring thing as well.
A lower-privileged account performs an action reserved for a higher one, which on a multi-author or membership site means an ordinary user reaching administrative behaviour. For Booking Calendar the fix is 10.10.1: builds <= 10.10 are affected, anything from 10.10.1 onward is not.
Remediation
Update to version 10.10.1, 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: Booking Calendar 10.10.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Booking Calendar
- 9.8CVE-2024-1207: Booking Calendar <= 9.9 SQL Injection
CVE-2024-1207 - 8.8CVE-2018-20556: Booking Calendar <= 8.4.3 SQL injection
CVE-2018-20556 - 8.8Booking Calendar <= 6.2 CSRF leading to Cross-Site Scripting
- 8.8Booking Calendar <= 6.2 Cross-Site Request Forgery to SQL Injection
- 8.5CVE-2022-1463: Booking Calendar <= 9.1 PHP Object Injection
CVE-2022-1463 - 7.5CVE-2025-14383: Booking Calendar <= 10.14.8 SQL Injection
CVE-2025-14383 - 7.2CVE-2026-59558: Booking Calendar <= 11.4.2 Stored Cross-Site Scripting
CVE-2026-59558 - 7.2Booking Calendar <= 6.2 SQL Injection
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C