# CVE-2026-89063: WordPress Bookly plugin insecure direct object reference in AI conversations

Source: https://junglewise.ai/threats/cve-2026-89063-wordpress-bookly-plugin-insecure-direct-object-reference-in-ai  
Publisher: Junglewise Threat Intelligence, https://junglewise.ai/threats  
Published: 2026-09-16. Updated: 2026-09-26  
License: CC BY 4.0 with a link back

CVE-2026-89063 · Severity: high · CVSS 7.5 · Published 2026-09-16

The Bookly appointment booking plugin for WordPress stores AI conversation transcripts containing sensitive customer data (names, emails, phone numbers, appointment details) without proper access controls. An unauthenticated attacker can read any customer's conversation history and inject malicious messages, potentially compromising customer privacy and allowing manipulation of appointment workflows.

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

## Quick answers

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

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

**Which products and versions are affected?** Bookly up to and including 28.1.

**Is there a fix for CVE-2026-89063?** 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-89063 attacked?** It is attacked over the network, in a software library.

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

The vulnerability is an Insecure Direct Object Reference (IDOR) in the AI conversation module, where the 'conversation_id' parameter lacks proper authorization validation. Because conversation IDs are sequential integers stored without owner, user, or session identifiers, unauthenticated attackers can enumerate and access any conversation by incrementing the parameter. An attacker can both read full transcripts (leaking PII) and inject arbitrary messages that are replayed to the Cloud AI worker with the complete private conversation history. No authentication is required to exploit this vulnerability.

## Affected products

- Bookly Bookly up to and including 28.1

## Timeline

- 2026-09-16: disclosed

## References

- [https://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.1/frontend/modules/ai/Ajax.php](https://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.1/frontend/modules/ai/Ajax.php)
- [https://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.1/frontend/modules/ai/Ajax.php](https://plugins.trac.wordpress.org/browser/bookly-responsive-appointment-booking-tool/tags/28.1/frontend/modules/ai/Ajax.php)

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