Booking Calendar WpDevArt <= 3.2.19 - Authenticated (Contributor+) SQL Injection
Strategic Overview
- Status
- Patched in 3.2.20
- Affected Plugin
- Booking calendar, Appointment Booking System
- Affected Version
<= 3.2.19- CVSS
- 6.5Medium
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2024-10856
At a glance
CVE-2024-10856 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Booking calendar, Appointment Booking System WordPress plugin, affecting versions <= 3.2.19. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 3.2.20; sites on affected versions should update now. Disclosed December 2024, reported by Peter Thaleikis.
Vulnerability Overview
The Booking Calendar WpDevArt plugin is vulnerable to time-based, blind SQL injection via the `id` parameter in the “wpdevart_booking_calendar” shortcode in versions up to, and including, 3.2.19 due to insufficient escaping on the user-supplied parameter and lack of sufficient preparation on the existing SQL query. The vulnerability requires the “delete_prev_date” theme option being enabled. This makes it possible for authenticated attackers, with contributor-level access or above, to append additional SQL queries into already existing query that can be used to extract sensitive information such as passwords from the database.
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.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Booking calendar, Appointment Booking System <= 3.2.19 carries this weakness at wpdevart_booking_calendar, and reaching it takes an account at Contributor level or above. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For Booking calendar, Appointment Booking System the fix is 3.2.20: builds <= 3.2.19 are affected, anything from 3.2.20 onward is not.
Remediation
Update to version 3.2.20, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor access first, so the firewall sees the attempt as traffic from a logged-in account: 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.20 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in Booking calendar, Appointment Booking System
- 9.8CVE-2022-3982: Booking calendar Arbitrary File Upload
CVE-2022-3982 - 8.8CVE-2018-5673: Booking calendar, Appointment Booking System CSRF
CVE-2018-5673 - 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 - 6.1CVE-2024-12077: Booking Calendar and Booking Calendar… Reflected XSS
CVE-2024-12077 - 5.5CVE-2022-47438: Booking calendar Stored XSS
CVE-2022-47438
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C