Online Scheduling and Appointment Booking System – Bookly <= 27.4 - Unauthenticated Information Exposure
Strategic Overview
- Status
- Patched in 27.5
- Affected Plugin
- Online Scheduling and Appointment Booking System – Bookly
- Affected Version
<= 27.4- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-42667
At a glance
CVE-2026-42667 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Online Scheduling and Appointment Booking System WordPress plugin, affecting versions <= 27.4. 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 27.5; sites on affected versions should update now. Disclosed May 2026, reported by Tiago Ventura (perses).
Vulnerability Overview
The Online Scheduling and Appointment Booking System – Bookly plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 27.4. 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 Online Scheduling and Appointment Booking System <= 27.4 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 Online Scheduling and Appointment Booking System the fix is 27.5: builds <= 27.4 are affected, anything from 27.5 onward is not.
Remediation
Update to version 27.5, 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: Online Scheduling and Appointment Booking System 27.5 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in Online Scheduling and Appointment Booking System – Bookly
- 8.1CVE-2023-26526: Bookly <= 21.7.1 Arbitrary File Deletion
CVE-2023-26526 - 7.5CVE-2026-13395: Online Scheduling and Appointment… SQL Injection
CVE-2026-13395 - 7.5CVE-2026-61949: Online Scheduling and Appointment… SQL Injection
CVE-2026-61949 - 7.2CVE-2026-61944: Online Scheduling and Appointment… Stored XSS
CVE-2026-61944 - 7.2CVE-2026-5513: Online Scheduling and Appointment… Stored XSS
CVE-2026-5513 - 7.2CVE-2023-1172: Bookly <= 21.5 Stored Cross-Site Scripting
CVE-2023-1172 - 7.2CVE-2018-6891: WordPress Online Booking… XSS
CVE-2018-6891 - 6.6CVE-2023-4691: Bookly <= 22.3.1 SQL Injection
CVE-2023-4691
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C