Summary
CVE-2026-42667 is a high-severity unauthenticated sensitive data exposure vulnerability affecting the Bookly WordPress plugin in all versions up to and including 27.4. Classified under CWE-201 (Insertion of Sensitive Information Into Sent Data), the flaw allows any remote, unauthenticated attacker to retrieve sensitive information directly from affected installations. With a CVSS v3.1 base score of 7.5 (HIGH) and over 60,000 active installations worldwide, this vulnerability presents significant risk to businesses relying on Bookly for appointment and scheduling management.
Technical details
- Root cause: The plugin inserts sensitive information into data sent in HTTP responses without enforcing authentication, classified as CWE-201 (Insertion of Sensitive Information Into Sent Data).
- Trigger conditions: An unauthenticated HTTP request to the affected endpoint is sufficient to trigger the data disclosure — no credentials, session token, or user interaction of any kind is required.
- Attack vector: Network-accessible; exploitable directly from the internet against any publicly reachable WordPress site running an affected version of the plugin.
- Impact: High confidentiality impact (C:H). The Bookly plugin manages customer booking records, contact details, service information, and appointment data, making exposed information potentially inclusive of customer personally identifiable information (PII). No integrity or availability impact has been reported.
Affected software
- Bookly – Online Scheduling and Appointment Booking System (WordPress plugin), all versions <= 27.4
Severity
- CVSS v3.1 Base Score: 7.5 (HIGH)
- Vector String:
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Mitigation and recommended actions
- Immediate action: Update the Bookly plugin to version 27.5 or later. The current available version is 27.7. Updates can be applied directly from the WordPress admin dashboard under Plugins → Installed Plugins → Update Available.
- If immediate patching is not possible:
- Restrict public network access to the WordPress installation using a web application firewall (WAF) rule to block unauthenticated requests to the affected endpoint.
IONIX Status
The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

