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