Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

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

Quick assessment

Affected
ladela Online Scheduling and Appointment Booking System – Bookly
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

WordPress 的 Bookly 插件在 28.2 及更早版本中存在不安全直接对象引用（Insecure Direct Object Reference, IDOR）漏洞，该漏洞可通过以下 AJAX 动作触发： 、 、 和 。 漏洞成因在于： 处理器盲目地将攻击者控制的 （来自提交的 ）存储到新创建的预订会话中；随后， 处理器在未验证该订单是否由当前会话创建的情况下，信任该 ，并据此查询和返回对应订单的保密令牌（secret token）。 这使得未经身份验证的攻击者能够： 枚举连续的订单 ID； 泄露其他客户

CVSS 9.1 · Critical EPSS 0.37% · P28
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-93399

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
Online Scheduling and Appointment Booking System <= 28.2 - Insecure Direct Object Reference to Unauthenticated Arbitrary Booking Token Disclosure and Deletion via 'order_id' Parameter
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
通过用户控制密钥绕过授权机制
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
ladela Online Scheduling and Appointment Booking System – Bookly 0 ~ 28.2 -

II. Public POCs for CVE-2026-93399

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-93399

请登录查看更多情报信息。

News Coverage for CVE-2026-93399 (1)

Other References for CVE-2026-93399 (7)

IV. Related Vulnerabilities

Same product: Online Scheduling and Appointment Booking System – Bookly
Same vendor: ladela
Same weakness: CWE-639

V. Comments for CVE-2026-93399

No comments yet

Leave a comment