Unauthenticated transcript disclosure and injection via sequential identifier
Published Sep 16, 2026 · Updated Sep 16, 2026
IDOR in Bookly 28.1 and earlier allows remote attackers to read and alter AI booking conversations through conversation_id. The AI Ajax.php handler uses a user-controlled sequential conversation identifier to retrieve and update transcripts without binding records to an owner, user, or session. No authentication is required, enabling enumeration of private customer details and injection of messages replayed to the Cloud AI worker.
Summary
What happened
IDOR in Bookly 28.1 and earlier allows remote attackers to read and alter AI booking conversations through conversation_id. The AI Ajax.php handler uses a user-controlled sequential conversation identifier to retrieve and update transcripts without binding records to an owner, user, or session. No authentication is required, enabling enumeration of private customer details and injection of messages replayed to the Cloud AI worker.
The record
- CVE
- CVE-2026-89063
- Published
- Sep 16, 2026
- Updated
- Sep 16, 2026
- Vendor
- Ladela Interactive
- Product
- Bookly
- Classifications
- CWE-639, T1213
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Sep 16, 2026CVE publishedPublication date reported by the CVE source.
- Sep 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=28.1
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo