Read the docs

Insecure object reference in LatePoint lets anyone read bookings

Priority LOW 39CWE-639Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
Security bypass
Confidentiality · integrity · availability
High · None · None
Fix status
No fix listed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-639.

Summary

The Appointment Booking Plugin (LatePoint) for WordPress is affected up to and including 5.7.3. Its public booking routes load booking and cart records by the booking[id] and cart[id] parameters without an ownership check, an authorization bypass through a user-controlled key (CWE-639). An unauthenticated remote attacker can enumerate sequential identifiers to read other customers' appointment details and pending checkout contents.

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Description from the CNA

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00475 41st percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
latepointAppointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPressup to 5.7.3—No fix listedCNA
  • Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress Vendorlatepoint Affected up to 5.7.3 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for the Appointment Booking Plugin (LatePoint | Calendar & Scheduling for WordPress).

Written with Claude Haiku 5.5 from the sources below · 2026-10-28

Timeline

  1. 2026-10-14 Threatist record created from CVE-2026-103366
  2. 2026-10-14 Alias added: GHSA-3pf7-5297-2ffv
  3. 2026-10-14 Priority changed: MEDIUM → LOW
  4. 2026-10-16 CISA SSVC decision points changed

References

  • TI-2026-86552 Authentication bypass in LatePoint lets attackers take over accounts CVSS 3.1CRITICAL 9.1
  • TI-2024-08303 LatePoint <= 5.0.12 - Authentication Bypass CVSS 3.1CRITICAL 9.8
  • TI-2024-08274 LatePoint <= 5.0.11 - Unauthenticated Arbitrary User Password Change via SQL Injection CVSS 3.1CRITICAL 9.8
  • TI-2026-62628 Appointment Booking Plugin <= 5.7.0 - Unauthenticated Arbitrary Shortcode Execution via First/Last Name Field CVSS 3.1CRITICAL 9.1
  • TI-2024-02298 LatePoint Plugin <= 4.9.9 - Missing Authorization and Sensitive Information Exposure via IDOR CVSS 3.1CRITICAL 9.1
  • TI-2026-76047 Race condition in LatePoint plugin allows authentication bypass CVSS 3.1CRITICAL 9.1
See all 48 →

Sources