PHP2Shell : See if you’re affected with a free external attack surface scan. Click Here > 

Back
New CVE Detected

CVE-2026-93399 – Unauthenticated IDOR / Data Disclosure & Destructive Booking Deletion – Bookly Word

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-93399 is a critical-severity (CVSS 9.1) Insecure Direct Object Reference (IDOR) vulnerability in the "Online Scheduling and Appointment Booking System – Bookly" WordPress plugin, affecting versions up to and including 28.2. The flaw lets unauthenticated attackers enumerate order IDs to disclose other customers’ order tokens and appointment details, and to permanently delete non-completed bookings, without any authentication or user interaction.

Technical details

  • Root cause: The bookly_get_form_id AJAX handler blindly stores an attacker-controlled order_id value (submitted in form_data) into a new booking session, without verifying that the requesting session actually created that order.
  • Trigger conditions: A subsequent call to bookly_render_complete trusts the tainted session data to look up and return the corresponding order’s secret token, with no ownership/session check against the original order.
  • Attack vector: Remote, network-based, no privileges and no user interaction required (AV:N/AC:L/PR:N/UI:N). An attacker simply submits sequential or guessed order IDs to the exposed AJAX actions bookly_get_form_id, bookly_render_complete, bookly_add_to_calendar, and bookly_rollback_order.
  • Impact: Enumeration of sequential order IDs; disclosure of other customers’ order secret tokens and calendar/appointment data via bookly_add_to_calendar; permanent deletion of arbitrary non-completed bookings via bookly_rollback_order, which cascades to delete the associated customer appointment record and, when no other customers remain attached, the underlying appointment itself. There is no confidentiality impact to plugin/site data beyond order tokens, but integrity and availability of booking data are both rated High.

Affected software

  • Online Scheduling and Appointment Booking System – Bookly (WordPress plugin), versions up to and including 28.2.

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
  • CWE-639: Authorization Bypass Through User-Controlled Key

Mitigation and recommended actions

  • Immediate: Upgrade the Bookly plugin to the latest version available from the WordPress.org plugin repository, which addresses the session/ownership validation flaw in the affected AJAX handlers. At the time of writing no fixed version number beyond 28.2 has been publicly confirmed — verify the installed version against the vendor’s changelog and update as soon as a fix is released.
  • If no patch is yet available: Restrict or monitor access to the Bookly AJAX endpoints (bookly_get_form_id, bookly_render_complete, bookly_add_to_calendar, bookly_rollback_order) at the WAF/reverse-proxy layer, alert on rapid sequential order_id requests, and consider disabling the Bookly public booking form until patched if the site handles sensitive customer data.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge