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.
References6
- plugins.trac.wordpress.org/browser/bookly-responsive-appointmen…
- plugins.trac.wordpress.org/browser/bookly-responsive-appointmen…
- plugins.trac.wordpress.org/browser/bookly-responsive-appointmen…
- plugins.trac.wordpress.org/browser/bookly-responsive-appointmen…
- plugins.trac.wordpress.org/browser/bookly-responsive-appointmen…
- www.wordfence.com/threat-intel/vulnerabilities/id/b6af015f-f954…
Metrics
- CVSS 3.1
-
7.5
HIGH
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - EPSS — exploit probability
- 2% percentile: 76 · as of 7 November 2026
- CWE
- CWE-639
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.