CVE-2026-93399
Authorization Bypass Through User-Controlled Key
Published Sep 25, 2026 · corrected/updated Sep 25, 2026 · ladela Online Scheduling and Appointment Booking System – Bookly · evidence confidence very high
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 possibl
Grounded briefings
Catalog interpretations for three audiences. Each brief cites ingested metadata and the original advisories below. They are not independent research and they do not invent exploit steps.
Executive
CVE-2026-93399 is a unknown public vulnerability record for ladela Online Scheduling and Appointment Booking System – Bookly. CISA lists it as known exploited. Published remediation guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. This summary is a catalog interpretation of the ingested metadata and cites the original advisories below.
System administrator
Identify whether ladela Online Scheduling and Appointment Booking System – Bookly is in your estate, then compare installed versions with the affected ranges. Affected packages or ranges on record: ladela Online Scheduling and Appointment Booking System – Bookly. Published remediation guidance: Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable. Prefer the vendor or distribution advisory linked in Sources before changing production systems. This is a catalog interpretation, not a runbook.
Security analyst
Signals on file: no CVSS/EPSS yet. CISA lists it as known exploited. Sources contributing to this record: vulncheck_kev. Public exploit references, when present, are outbound links only and are not proof of active exploitation. This is a catalog interpretation of stored metadata.
Exploitation and remediation
Exploitation evidence
Confirmed in CISA KEV since Sep 25, 2026. Listed in CISA KEV and VulnCheck KEV.
Patch and remediation
Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Safe detection guidance
Compare installed versions with the affected ranges below and verify the advisory from the original publisher. This site stores metadata and outbound links only; it does not ship exploit code or proof-of-concept payloads.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
No public source repository is identified for this product.
Timeline
Detection, updates, and resolution for this record.
Sep 25, 2026 · VulnCheck KEV
Detected
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,
Sep 25, 2026 · CISA KEV
Known exploited
Apply remediations or mitigations per vendor instructions or discontinue use of the product if remediation or mitigations are unavailable.
Affected
- vendor ladela Online Scheduling and Appointment Booking System – Booklyversion unspecified
Sources
- VulnCheck KEVConfirmed exploitationCVE-2026-93399
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_
vulncheck.com