CVE-2026-93399: Online Scheduling and Appointment Booking System <= 28.2 - Insecure Direct Object Reference to Unauthenticated Arbitrary Booking Token Disclosure and Deletion via 'order_id' Parameter
The Bookly plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 28.2 via the 'booklygetformid', 'booklyrendercomplete', 'booklyaddtocalendar' and 'booklyrollbackorder' AJAX actions. This is due to the 'booklygetformid' handler blindly storing the attacker-controlled 'orderid' from the submitted formdata into a new booking session, which the 'booklyrendercomplete' handler then trusts to look up and return the corresponding Order's secret token without verifying that the current session created that order. This makes it possible for unauthenticated attackers to enumerate sequential order IDs, disclose other customers' order tokens, retrieve calendar/appointment information via 'booklyaddtocalendar' and permanently delete arbitrary non-completed bookings via 'booklyrollbackorder', which cascade-deletes the customerappointment and (when no other customers are attached) the underlying appointment.
Affected Software
Event History
Frequently Asked Questions
Who can exploit this issue?
Unauthenticated remote attackers can exploit it; no login or user interaction is required. They can enumerate sequential order IDs to target other customers' bookings.
What information and actions can an attacker obtain through a disclosed booking token?
An attacker can disclose an order's secret token and use it to retrieve calendar or appointment information through the bookly_add_to_calendar action. They can also permanently delete arbitrary bookings that are not completed through bookly_rollback_order.
What is deleted when a booking is rolled back?
Rolling back a targeted non-completed booking cascade-deletes its customer_appointment record. If no other customers are attached to the appointment, the underlying appointment is also deleted.
Which functionality is involved in the vulnerable flow?
The affected AJAX actions are bookly_get_form_id, bookly_render_complete, bookly_add_to_calendar, and bookly_rollback_order. The issue arises because an attacker-controlled order_id is stored in a new booking session and later trusted without verifying that the session created that order.