CVE-2026-17538: Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress · Insecure Direct Object Reference
Affects Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPressSource CVE Database V5
Not known to be exploited · CVSS 5.4 Medium.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 4% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 7 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 21 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| latepointAppointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress | Affected
| Fixed in– |
AI-suggested
Until a fix is available, restrict user roles and permissions to trusted users only and monitor for suspicious activity related to customer data modification. Avoid using the 'phone' setting for contact_merge if possible, as it increases risk of account takeover. Follow vendor updates closely for an official fix.
Description
The LatePoint Appointment Booking plugin for WordPress up to version 5.6.9 contains an authorization bypass vulnerability. Authenticated users with Subscriber-level access or higher can modify personal information of arbitrary customers due to insufficient ownership checks in the process_step_customer() function. This flaw allows attackers to change details such as first name, last name, email, phone, and notes. When the contact_merge setting is configured to 'phone', attackers can overwrite the victim's email address and potentially take over the account via password reset.