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
ladela · Online Scheduling and Appointment Booking System – Bookly
Affected: ladela Online Scheduling and Appointment Booking System – Bookly · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 48% of scored CVEs
DescriptionCVE.org
The Bookly plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 28.2 via the 'bookly_get_form_id', 'bookly_render_complete', 'bookly_add_to_calendar' and 'bookly_rollback_order' AJAX actions. This is due to the 'bookly_get_form_id' handler blindly storing the attacker-controlled 'order_id' from the submitted form_data into a new booking session, which the 'bookly_render_complete' 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 'bookly_add_to_calendar' and permanently delete arbitrary non-completed bookings via 'bookly_rollback_order', which cascade-deletes the customer_appointment and (when no other customers are attached) the underlying appointment.
Affected products1
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- ladela · Online Scheduling and Appointment Booking System – Booklyup to and including 28.2
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Weakness
- Insecure Direct Object Reference
- Vendor
- ladela
- Published
- September 2026
CoverageNo articles yet
No CyberSIXT article names CVE-2026-93399 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.
References
- NVD entrynvd.nist.gov
- CVE recordcve.org
- Weakness CWE-639cwe.mitre.org
- wordfence.com/threat-intel/vulnerabilities/id/d45a01e5-0e69-4d95wordfence.com
- plugins.trac.wordpress.org/browser/bookly-responsive-appointmentplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/bookly-responsive-appointmentplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/bookly-responsive-appointmentplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/bookly-responsive-appointmentplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/bookly-responsive-appointmentplugins.trac.wordpress.org
- plugins.trac.wordpress.org/browser/bookly-responsive-appointmentplugins.trac.wordpress.org
- plugins.trac.wordpress.org/changeset?reponame=&old=3707284%40booplugins.trac.wordpress.org