ZeroHour

CVE-2026-89063

moderate

Unauthenticated IDOR in Bookly WordPress Plugin Exposes AI Booking Chats

CVSS 3.1
7.5 high
EPSS
Published
()
Modified
AI analysis

The Online Scheduling and Appointment Booking System – Bookly plugin for WordPress is vulnerable to an insecure direct object reference in all versions up to and including 28.1, via the 'conversation_id' parameter, which has no ownership, user, or session validation and uses sequential integer IDs. Any unauthenticated attacker can enumerate every customer conversation simply by incrementing the parameter and read full AI booking transcripts, leaking names, email addresses, phone numbers, and appointment details echoed by the assistant. Attackers can additionally inject arbitrary messages into any victim's conversation, which are subsequently replayed to the Cloud AI worker along with the victim's complete private history, enabling manipulated or phishing-style bookings. Any WordPress site running Bookly 28.1 or earlier with the AI booking conversation feature in use is affected. No public proof-of-concept exists and the flaw is not in CISA's KEV, so exploitation is currently none known.

What to do: Update to the latest Bookly release immediately (any patched version above 28.1), or disable the AI booking assistant feature until the update is applied. Review web server and plugin logs for unauthenticated requests iterating sequential conversation_id values, and audit stored AI transcripts for unexpected injected messages. Because customer names, emails, phone numbers, and appointment details may have been exposed, assess breach-notification obligations for affected individuals.

Affected
Bookly Online Scheduling and Appointment Booking System – Bookly (WordPress plugin)All versions up to and including 28.1
Estimated exposure
moderatetens of thousands of sites at most (≈90,000+ sites run Bookly, but only those with the AI conversation feature enabled are exploitable) — The free Bookly plugin's publicly listed WordPress.org active-install count is roughly 90,000+, and the vulnerable AI-assistant conversation code path is a newer, optional feature likely enabled on only a fraction of those installations.

Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.

Description

The Online Scheduling and Appointment Booking System – Bookly plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 28.1 via the 'conversation_id' parameter due to missing validation on a user controlled key. This makes it possible for unauthenticated attackers to read the full AI booking conversation transcript of any customer — leaking names, email addresses, phone numbers, and appointment details echoed by the assistant — and inject arbitrary messages into any victim conversation that are subsequently replayed to the Cloud AI worker along with the full private history. Because AI conversations are stored with no owner, user, or session identifier and conversation IDs are sequential integers, an unauthenticated attacker can enumerate all customer conversations simply by incrementing the conversation_id parameter.

Ecosystems
WordPress
Weakness
CWE-639
Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

In the news

No ingested article mentions this CVE yet.