# CVE-2026-93399: Information disclosure in Online Scheduling and Appointment Booking System – Bookly

> Unauthenticated attackers can disclose booking tokens and delete arbitrary appointments via insecure direct object reference in the Bookly WordPress plugin.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 26 Sep 2026
- **Also known as:** GHSA-rmc5-xv4j-mvf8

## What is CVE-2026-93399?

CVE-2026-93399 is a critical vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-93399?


## How do I fix CVE-2026-93399?

No fix has been published for CVE-2026-93399 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-93399 being exploited?

There is no known exploitation of CVE-2026-93399 in the wild and no public exploit code.

Public exploit code:

- Unauthenticated IDOR in Bookly ≤ 28.2: bookly_get_form_id + bookly_render_complete leak any order’s bookly_order token; bookly_add_to_calendar exposes appointments; bookly_rollback_order cancels/deletes non-completed bookings. CVSS 9.1. Python check/exploit PoC — pocbit.org/pocs/cve-2026-93399 (github_poc): https://github.com/murrez/CVE-2026-93399
- Bookly <= 28.2 Unauth IDOR + PII Leak + RCE  Mass exploitation scanner for CVE-2026-93399 (CVSS 9.1 Critical) affecting the Bookly — Online Scheduling and Appointment Booking System WordPress plugin (versions <= 28.2). (github_poc): https://github.com/josemour8/CVE-2026-93399

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-93399 and fix it if it is affected.

What it is: CVE-2026-93399 is a critical vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 25 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93399 in the wild and no public exploit code.

Affected product: ladela Online Scheduling and Appointment Booking System – Bookly. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-93399/ (Markdown: https://insights.sbomify.com/CVE-2026-93399/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-93399
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-93399
- OSV: https://osv.dev/vulnerability/CVE-2026-93399

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-93399/
Summaries are generated and may contain mistakes; the official description above is the record.