Booking Calendar < 11.8 - Unauthenticated Information Exposure
Strategic Overview
- Status
- Patched in 11.8
- Affected Plugin
- Booking Calendar
- Affected Version
< 11.8- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-105193
At a glance
CVE-2026-105193 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Booking Calendar WordPress plugin, affecting versions < 11.8. 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 11.8; sites on affected versions should update now. Disclosed October 2026, reported by Olaf Schigt.
Vulnerability Overview
The Booking Calendar plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to 11.8. This makes it possible for unauthenticated attackers to extract sensitive user or configuration data.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in Booking Calendar < 11.8 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Booking Calendar the fix is 11.8: builds < 11.8 are affected, anything from 11.8 onward is not.
Remediation
Update to version 11.8, 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 11.8 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-92619: Booking Calendar Privilege Escalation
CVE-2026-92619 - 7.2CVE-2026-59558: Booking Calendar <= 11.4.2 Stored Cross-Site Scripting
CVE-2026-59558
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C