Read the docs

Authentication bypass in LatePoint plugin allows customer takeover

Priority LOW 35CWE-287Published · Updated

Key facts

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

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

Summary

Appointment Booking Plugin (LatePoint) up to and including 5.7.2 has an improper authentication flaw (CWE-287). With the 'Use WordPress users as customers' option enabled, a WordPress user whose login equals a customer's email is linked to that customer without checking the user's email. An attacker with Subscriber-level access can take over another customer's account and read its bookings and calendar data.

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 Authentication Bypass in versions up to, and including, 5.7.2 via the OsCustomerHelper::create_wp_user_for_customer() helper reached from the public process_step_customer() booking step. When the 'Use WordPress users as customers' option is enabled, the helper falls back from email_exists() to username_exists( $customer->email ), which matches any WordPress user whose user_login equals the victim customer's email even when that user's user_email is completely different, and links that WordPress user's ID into the victim's LatePoint customer row (only privileged roles are excluded; Subscriber is allowed). This makes it possible for authenticated attackers, with Subscriber-level access and above, to take over another customer's LatePoint account — accessing their bookings, service, agent, and calendar data, and having the victim customer's email overwritten with the attacker's on next login — by holding a Subscriber account whose user_login equals the victim's email and submitting an unauthenticated public booking step registration request.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00431 37th 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
No
Technical impact
Total

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.2—No fix listedCNA
  • Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress Vendorlatepoint Affected up to 5.7.2 Fixed in — No fix listed CNA

Remediation

The sources list no fixed version for Appointment Booking Plugin (LatePoint).

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

Timeline

  1. 2026-10-14 Threatist record created from CVE-2026-100163
  2. 2026-10-14 Alias added: GHSA-fwf2-rqrw-2q37
  3. 2026-10-14 Priority changed: MEDIUM → LOW
  4. 2026-10-15 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