Booking calendar, Appointment Booking System <= 3.2.3 - Cross-Site Request Forgery
Strategic Overview
- Status
- Patched in 3.2.4
- Affected Plugin
- Booking calendar, Appointment Booking System
- Affected Version
<= 3.2.3- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2023-24388
At a glance
CVE-2023-24388 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Booking calendar, Appointment Booking System WordPress plugin, affecting versions <= 3.2.3. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.2.4; sites on affected versions should update now. Disclosed January 2023, reported by yuyudhn.
Vulnerability Overview
The Booking calendar plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 3.2.3. This is due to missing or incorrect nonce validation when creating, editing, duplicating and deleting bookings. This makes it possible for unauthenticated attackers to manipulate bookings using these actions via forged request granted they can trick an administrator into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Booking calendar, Appointment Booking System <= 3.2.3 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Booking calendar, Appointment Booking System the fix is 3.2.4: builds <= 3.2.3 are affected, anything from 3.2.4 onward is not.
Remediation
Update to version 3.2.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Booking calendar, Appointment Booking System: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Booking calendar, Appointment Booking System 3.2.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Booking calendar, Appointment Booking System
- 9.8CVE-2022-3982: Booking calendar Arbitrary File Upload
CVE-2022-3982 - 7.5CVE-2018-10363: Booking calendar Parameter Manipulation
CVE-2018-10363 - 7.2CVE-2026-14334: Booking calendar Stored XSS
CVE-2026-14334 - 7.2CVE-2026-25435: Booking calendar Stored XSS
CVE-2026-25435 - 7.2CVE-2024-9504: Booking calendar, Appointment Booking System Stored XSS
CVE-2024-9504 - 7.2Booking Calendar WpDevArt <= 3.2.11 SQL Injection
- 7.2Booking calendar Multiple Authenticated(Editor+) SQL Injection
- 7.2CVE-2022-47428: Booking calendar SQL Injection
CVE-2022-47428
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C