Quick answers
- Is CVE-2026-93399 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-93399 being exploited in the wild.
- How severe is CVE-2026-93399?
- Critical severity, with a CVSS score of 9.1, published 25 September 2026.
- Which products and versions are affected?
- Bookly up to and including 28.2.
- Is there a fix for CVE-2026-93399?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-93399 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-93399?
- Check whether you run Bookly at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in multiple AJAX handlers (bookly_get_form_id, bookly_render_complete, bookly_add_to_calendar, bookly_rollback_order) that trust attacker-controlled order_id parameters without verifying ownership or proper authorization. The bookly_get_form_id handler stores user-supplied order_id into a session, which bookly_render_complete then uses to retrieve order tokens without checking if the current session created that order. This allows unauthenticated attackers to enumerate order IDs and access sensitive booking information across customers.
Affected products
- Bookly Bookly up to and including 28.2
Timeline
- 2026-09-25: disclosed: CVE-2026-93399 published on NVD