# CVE-2026-96348: Bookly broken access control in appointment booking

Source: https://junglewise.ai/threats/cve-2026-96348-unauthenticated-broken-access-control-in-bookly-28-2-versions  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-30. Updated: 2026-09-30  
License: CC BY 4.0 with a link back

CVE-2026-96348 · Severity: high · CVSS 7.5 · Published 2026-09-30

Bookly is a WordPress plugin that handles appointment booking and scheduling for service providers. An unauthenticated vulnerability allows attackers to bypass access controls and view or perform actions they should not be authorized for, such as accessing other users' appointment data or modifying bookings without proper credentials.

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

## Quick answers

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

**How severe is CVE-2026-96348?** High severity, with a CVSS score of 7.5, published 30 September 2026.

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

**Is there a fix for CVE-2026-96348?** A patch was published on 2026-09-30: Version 28.3 and later Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

**How is CVE-2026-96348 attacked?** It is attacked over the network.

**Am I affected by CVE-2026-96348?** 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

Broken access control vulnerability in Bookly <= 28.2 allows unauthenticated attackers to access restricted functionality and data. The vulnerability stems from insufficient authorization checks on sensitive operations, enabling attackers to view or manipulate appointments and user information without authentication. The issue is fixed in version 28.3.

## Affected products

- Bookly Bookly <=28.2

## Timeline

- 2026-09-24: disclosed
- 2026-09-30: patched: Version 28.3 and later

## References

- [https://wordpress.org/plugins](https://wordpress.org/plugins)
- [https://patchstack.com/database/wordpress/plugin/bookly-responsive-appointment-booking-tool/vulnerability/wordpress-bookly-plugin-28-2-broken-access-control-vulnerability?_s_id=cve](https://patchstack.com/database/wordpress/plugin/bookly-responsive-appointment-booking-tool/vulnerability/wordpress-bookly-plugin-28-2-broken-access-control-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 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)
- [Bookly appointment booking plugin IDOR in AI assistant conversations](https://junglewise.ai/threats/cve-2026-91847-the-online-scheduling-and-appointment-booking-system-wordpress)