Online Scheduling and Appointment Booking System <= 28.1 - Insecure Direct Object Reference to Unauthenticated Sensitive Data Access and Message Injection via 'conversation_id' Parameter

7.5
Authorization Bypass Through User-Controlled Key
CVE CVE-2026-89063
CVSS 7.5 (High)
Publicly Published September 15, 2026
Last Updated September 16, 2026
Researcher jtb75 - NG20 LLC

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.

References

Share

Vulnerability Details for Online Scheduling and Appointment Booking System – Bookly

Software Type Plugin
Software Slug bookly-responsive-appointment-booking-tool (view on wordpress.org)
Patched? Yes
Remediation Update to version 28.2, or a newer patched version
Affected Version
  • <= 28.1
Patched Version
  • 28.2

Recent vulnerabilities in Online Scheduling and Appointment Booking System – Bookly

# Title CVE ID CVSS Researchers Date
1 Online Scheduling and Appointment Booking System <= 28.2 - Authenticated (Custom+) PHP Object Injection via 'value' Parameter CVE-2026-12626 7.2 Muni Nitish Kumar Yaddala (Stranger825) October 9, 2026
2 Online Scheduling and Appointment Booking System <= 28.4 - Insecure Direct Object Reference to Authenticated (Subscriber+) Privilege Escalation via 'id' and 'wp_user_id' Parameters via Query String / JSON Body CVE-2026-104898 6.8 Wordfence PRISM October 9, 2026
3 Online Scheduling and Appointment Booking System <= 28.4 - Unauthenticated Sensitive Information Exposure in 'phone' Parameter to bookly_render_details CVE-2026-103365 5.3 R3D October 9, 2026
4 Bookly <= 28.2 - Authenticated (Staff+) Insecure Direct Object Reference CVE-2026-86839 4.3 Vũ Quang Huy September 25, 2026
5 Bookly <= 28.2 - Unauthenticated Payment Bypass CVE-2026-86838 5.3 vuxvinh September 25, 2026
6 Bookly <= 28.2 - Unauthenticated Insecure Direct Object Reference CVE-2026-86837 5.3 Artus KG September 25, 2026
7 Bookly 23.2 - 28.2 - Authenticated (Bookly Administrator+) PHP Object Injection CVE-2026-86841 7.5 Muni Nitish Kumar Yaddala September 25, 2026
8 Online Scheduling and Appointment Booking System <= 28.2 - Insecure Direct Object Reference to Unauthenticated Arbitrary Booking Token Disclosure and Deletion via 'order_id' Parameter CVE-2026-93399 9.1 Theklis September 24, 2026
9 Online Scheduling and Appointment Booking System <= 28.2 - Unauthenticated Authorization Bypass via PHP Type Juggling via 'verification_code' Parameter Type Juggling via json_data CVE-2026-92799 5.3 crow September 24, 2026
10 Online Scheduling and Appointment Booking System – Bookly <= 28.2 - Missing Authorization CVE-2026-96348 5.3 Ananda Dhakal September 24, 2026

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation