# CVE-2026-91847: Bookly appointment booking plugin IDOR in AI assistant conversations

Source: https://junglewise.ai/threats/cve-2026-91847-the-online-scheduling-and-appointment-booking-system-wordpress  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-19. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-91847 · Severity: medium · CVSS 4.8 · Published 2026-09-19

Bookly is a WordPress plugin that manages appointment booking and scheduling. An unauthenticated attacker can read another visitor's AI assistant conversation messages and inject their own messages into an active conversation due to missing ownership verification. This allows exposure of customer scheduling details and conversation data without authentication.

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

## Quick answers

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

**How severe is CVE-2026-91847?** Medium severity, with a CVSS score of 4.8, published 19 September 2026.

**Which products and versions are affected?** Bookly before 28.2.

**Is there a fix for CVE-2026-91847?** A patch was published on 2026-09-19: Fixed in version 28.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

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

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

An Insecure Direct Object Reference (IDOR) vulnerability exists in unauthenticated conversation actions where the plugin fails to verify that the requester owns the AI booking-assistant conversation ID. Attackers can access conversation endpoints with arbitrary conversation identifiers to read and write messages without authentication. This is a broken access control flaw allowing complete compromise of conversation confidentiality and integrity.

## Affected products

- Bookly Bookly before 28.2

## Timeline

- 2026-09-19: disclosed
- 2026-09-19: patched: Fixed in version 28.2

## References

- [https://wpscan.com/vulnerability/9eef3086-3a67-4ee2-bd78-e346e7b05d62/](https://wpscan.com/vulnerability/9eef3086-3a67-4ee2-bd78-e346e7b05d62/)

## 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)