WordPress Booking Plugin Insecure Object Reference Flaw

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, p

Casky was already ahead

This CVE exploits attack patterns that Casky's 283matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The LatePoint appointment booking plugin for WordPress contains an Insecure Direct Object Reference (IDOR) vulnerability affecting versions up to 5.7.3. Attackers can manipulate booking and cart ID parameters in public AJAX routes to access, modify, or delete appointment records belonging to other users without authorization. This vulnerability is particularly dangerous because the affected endpoints (`steps__reload_booking_form_summary_panel` and `steps__start`) are reachable through `wp_ajax_nopriv_latepoint_route_call`, meaning unauthenticated attackers can exploit it. Any WordPress site running this plugin with active appointment booking functionality exposes sensitive customer data, appointment details, and payment information to unauthorized access.

Casky.ai's 283 matched security skills leverage Claude's extended reasoning to detect attack patterns across MITRE ATT&CK techniques TA0004 (Privilege Escalation) and TA0006 (Credential Access). Practitioners using Casky would identify suspicious patterns such as: sequential or randomized booking ID enumeration attempts in AJAX logs, anomalous access to booking summaries from unauthenticated sessions, parameter tampering indicators in wp_ajax_nopriv calls, and cross-user data access without proper session validation. The platform's skill mapping would flag the absence of object-level authorization checks in the `OsStepsHelper::set_required_objects()` function and highlight how raw request parameters bypass access control logic—enabling security teams to prioritize remediation and hunt for active exploitation in their WordPress environments.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

283 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-103366.

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

Access with Stolen Session Cookie

identity access management · low

Run

MITRE ATT&CK Techniques

TA0004 TA0006

Investigate the attack patterns behind CVE-2026-103366

Casky has 283 skills that investigate the attack patterns behind CVE-2026-103366. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn