# CVE-2026-42667: Bookly WordPress plugin sensitive data exposure

Source: https://junglewise.ai/threats/cve-2026-42667-bookly-wordpress-plugin-sensitive-data-exposure  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-06-15. Updated: 2026-06-15  
License: CC BY 4.0 with a link back

CVE-2026-42667 · Severity: high · CVSS 7.5 · Published 2026-06-15

The Bookly plugin for WordPress, which is used for managing online appointments and bookings, contains a security flaw that allows unauthorized individuals to access sensitive information. An attacker could exploit this to view data that should be private, potentially leading to further attacks or the exposure of customer details. This issue affects all versions of the plugin up to and including 27.4.

Technologies: [Bookly](https://junglewise.ai/threats/technologies/bookly). Vendors: [Bookly](https://junglewise.ai/threats/vendors/bookly).

## Quick answers

**Is CVE-2026-42667 exploited in the wild?** No. Junglewise Threat Intelligence has no report of CVE-2026-42667 being exploited in the wild.

**How severe is CVE-2026-42667?** High severity, with a CVSS score of 7.5, published 15 June 2026.

**Which products and versions are affected?** Bookly <= 27.4.

**Is there a fix for CVE-2026-42667?** No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.

**How is CVE-2026-42667 attacked?** It is attacked over the network, in a software library.

**Am I affected by CVE-2026-42667?** Check whether you run Bookly at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

## Technical details

A sensitive data exposure vulnerability (CWE-201) exists in the Bookly plugin for WordPress through version 27.4. The flaw allows an unauthenticated remote attacker to access sensitive information that is normally restricted to authorized users. This occurs because the application improperly includes sensitive data in responses sent to unauthenticated users. An attacker can exploit this over the network without any user interaction. The vulnerability is resolved in version 27.5.

## Affected products

- Bookly Bookly <= 27.4

## Timeline

- 2026-04-10: other: Reported by Tiago Ventura (@perses)
- 2026-05-10: advisory: Patchstack advisory published
- 2026-06-15: disclosed: NVD publication date

## References

- [https://patchstack.com/database/wordpress/plugin/bookly-responsive-appointment-booking-tool/vulnerability/wordpress-bookly-plugin-27-4-sensitive-data-exposure-vulnerability?_s_id=cve](https://patchstack.com/database/wordpress/plugin/bookly-responsive-appointment-booking-tool/vulnerability/wordpress-bookly-plugin-27-4-sensitive-data-exposure-vulnerability?_s_id=cve)

## Related threats

- [Bookly plugin for WordPress PHP Object Injection](https://junglewise.ai/threats/cve-2026-12626-the-online-scheduling-and-appointment-booking-system-bookly)
- [Bookly broken access control in appointment booking](https://junglewise.ai/threats/cve-2026-96348-unauthenticated-broken-access-control-in-bookly-28-2-versions)
- [Bookly Insecure Direct Object References (IDOR) in Subscriber access](https://junglewise.ai/threats/cve-2026-96347-subscriber-insecure-direct-object-references-idor-in-bookly-28-2)
- [Bookly WordPress plugin payment bypass via booking price manipulation](https://junglewise.ai/threats/cve-2026-86838-the-bookly-wordpress-plugin-before-28-3-does-not-validate-client)
- [Bookly Insecure Direct Object Reference in AJAX handlers](https://junglewise.ai/threats/cve-2026-93399-the-bookly-plugin-for-wordpress-is-vulnerable-to-insecure-direct)