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

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-103366— Appointment Booking Plugin <= 5.7.3 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Disclosure via 'booking[id]' and 'cart[id]' Parameters

Quick assessment

Affected
latepoint Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress
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 的 Appointment Booking Plugin – LatePoint 漏洞成因在于： 将未经验证的原始请求参数直接传入 和 函数，而这两个函数会调用 ，通过主键加载任意预订或购物车记录，且未进行任何所有权验证。尽管厂商此前为修复相关披露问题而在 中添加了所有权保护机制，但该保护并未覆盖上述并列路由，也未对 提供任何防护。 因此，未经身份验证的攻击者可以枚举连续的预订 ID 或购物车 ID，并直接从 JSON 响应中读取其他客户的预约详情（包括服务名称、服务人员、日期/时间、持续时间、

CVSS 7.5 · High EPSS 0.47% · P40

Affected Version Matrix 1

VendorProduct Version RangeStatus
latepoint Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress ≤ 5.7.3 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-103366

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
Appointment Booking Plugin <= 5.7.3 - Insecure Direct Object Reference to Unauthenticated Sensitive Information Disclosure via 'booking[id]' and 'cart[id]' Parameters
Source: CVE Program / CVE List V5
Vulnerability Description
The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 5.7.3 via the `booking[id]` and `cart[id]` parameters on the `steps__reload_booking_form_summary_panel` and `steps__start` public routes (reachable through wp_ajax_nopriv_latepoint_route_call). This is due to `OsStepsHelper::set_required_objects()` feeding raw request parameters into `set_booking_object()` and `set_cart_object()`, which call `OsModel::set_data()` and load an arbitrary booking or cart row by primary key with no ownership check — the ownership guard the vendor added for the earlier disclosure lives only inside `OsStepsHelper::load_step()` and does not cover the sibling routes or `cart[id]` at all. This makes it possible for unauthenticated attackers to enumerate sequential booking / cart identifiers and read other customers' appointment details (service name, agent, date/time, duration, price breakdown, status) and other shoppers' pending checkout contents directly from the JSON responses.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Source: CVE Program / CVE List V5
Vulnerability Type
通过用户控制密钥绕过授权机制
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
latepoint Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress 0 ~ 5.7.3 -

II. Public POCs for CVE-2026-103366

# 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-103366

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

Patches & Fixes for CVE-2026-103366 (1)

Other References for CVE-2026-103366 (3)

Same Patch Batch · latepoint · 2026-10-14 · 3 CVEs total

CVE-2026-100163 7.4 HIGH Appointment Booking Plugin <= 5.7.2 - Unauthenticated Authentication Bypass to Customer Ac
CVE-2026-103380 4.3 MEDIUM Appointment Booking Plugin <= 5.7.3 - Authenticated (Subscriber+) Sensitive Information Ex

IV. Related Vulnerabilities

Same product: Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress
Same vendor: latepoint
Same weakness: CWE-639

V. Comments for CVE-2026-103366

No comments yet

Leave a comment