Booking Calendar <= 10.14.13 - Missing Authorization to Unauthenticated Booking Details Exposure
Strategic Overview
- Status
- Patched in 10.14.14
- Affected Plugin
- Booking Calendar
- Affected Version
<= 10.14.13- CVSS
- 5.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-1431
At a glance
CVE-2026-1431 is a medium-severity Missing Authorization vulnerability in the Booking Calendar WordPress plugin, affecting versions <= 10.14.13. 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.14.14; sites on affected versions should update now. Disclosed January 2026, reported by type5afe.
Vulnerability Overview
The Booking Calendar plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the wpbc_ajax_WPBC_FLEXTIMELINE_NAV() function in all versions up to, and including, 10.14.13. This makes it possible for unauthenticated attackers to retrieve booking information including customer names, phones and emails.
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-862: Missing Authorization
Booking Calendar <= 10.14.13 carries this weakness at wpbc_ajax_WPBC_FLEXTIMELINE_NAV(), and reaching it takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Booking Calendar the fix is 10.14.14: builds <= 10.14.13 are affected, anything from 10.14.14 onward is not.
Remediation
Update to version 10.14.14, 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.14.14 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
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