Customer data exposure in LatePoint Appointment Booking plugin
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- High
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-200.
Summary
The Appointment Booking Plugin: LatePoint | Calendar & Scheduling for WordPress is affected in all versions up to and including 5.7.4. Improper handling of the customer[uuid] parameter exposes customer records (CWE-200). An unauthenticated remote attacker enumerates uuid prefixes via the steps__load_step AJAX endpoint to read customer first names, last names, emails, phone numbers and notes. This applies only when Field used for authentication is set to Disable ability to login.
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 Sensitive Information Exposure in all versions up to, and including, 5.7.4 via the 'params (customer[uuid])' parameter. This makes it possible for unauthenticated attackers to extract the first name, last name, email address, phone number, and notes of every customer record in the database by enumerating uuid prefixes via the unauthenticated steps__load_step AJAX endpoint. This vulnerability is only exploitable when the LatePoint plugin is configured with the 'Field used for authentication' setting set to 'Disable ability to login' (guest checkout mode).
Why it matters now
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| latepoint | Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress | up to 5.7.4 | — | No fix listed | CNA |
- Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress Vendorlatepoint Affected up to 5.7.4 Fixed in — No fix listed CNA
Remediation
The sources list no fixed version for Appointment Booking Plugin: LatePoint | Calendar & Scheduling for WordPress.
Written with Claude Haiku 5.5 from the sources below · 2026-10-28
Timeline
- 2026-10-18 Threatist record created from CVE-2026-111602
- 2026-10-18 Alias added: GHSA-x9g8-c97m-r8x5
References
Other 6
- https://www.wordfence.com/threat-intel/vulnerabilities/id/6afce24f-30cd-4aeb-a5dd-20bd80a75779?source=cve
- https://plugins.trac.wordpress.org/browser/latepoint/tags/5.7.4/lib/helpers/steps_helper.php#L1175
- https://plugins.trac.wordpress.org/browser/latepoint/tags/5.7.4/lib/controllers/steps_controller.php#L355
- https://plugins.trac.wordpress.org/browser/latepoint/tags/5.7.4/lib/models/model.php#L379
- https://plugins.trac.wordpress.org/browser/latepoint/tags/5.7.4/lib/helpers/params_helper.php#L14
- https://plugins.trac.wordpress.org/browser/latepoint/tags/5.7.5/lib/controllers/steps_controller.php
More latepoint vulnerabilities
- 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
Sources
- CVE-2026-111602 · CVE Program
- CVE-2026-111602 · NVD
- FIRST EPSS
- GHSA-x9g8-c97m-r8x5 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences