Booking Calendar <= 10.14.15 - Authenticated (Editor+) SQL Injection
Strategic Overview
- Status
- Patched in 10.14.16
- Affected Plugin
- Booking Calendar
- Affected Version
<= 10.14.15- CVSS
- 4.9Medium
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2026-32358
At a glance
CVE-2026-32358 is a medium-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the Booking Calendar WordPress plugin, affecting versions <= 10.14.15. It carries a CVSS score of 4.9 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires an authenticated account at Editor level or above. The issue is fixed in version 10.14.16; sites on affected versions should update now. Disclosed February 2026, reported by Drew Webber (mcdruid).
Vulnerability Overview
The Booking Calendar plugin for WordPress is vulnerable to SQL Injection in versions up to, and including, 10.14.15 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for authenticated attackers, with editor-level access and above, to append additional SQL queries into already existing queries that can be used to extract sensitive information 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')
Reaching this weakness in Booking Calendar <= 10.14.15 takes an account at Editor 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 the fix is 10.14.16: builds <= 10.14.15 are affected, anything from 10.14.16 onward is not.
Remediation
Update to version 10.14.16, or a newer patched version
How does WordSec protect against this?
An attacker needs Editor 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 10.14.16 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
- 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.2CVE-2026-59558: Booking Calendar <= 11.4.2 Stored Cross-Site Scripting
CVE-2026-59558 - 6.6CVE-2023-23991: Booking Calendar <= 9.4.2 SQL Injection
CVE-2023-23991 - 6.5CVE-2023-4620: Booking Calendar <= 9.7.3 Stored Cross-Site Scripting
CVE-2023-4620 - 6.4CVE-2025-12804: Booking Calendar <= 10.14.6 Stored XSS
CVE-2025-12804 - 6.4CVE-2025-64381: Booking Calendar <= 10.14.7 Stored XSS
CVE-2025-64381
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C