Skip to main content

LatePoint CVE-2026-17538

| EUVDEUVD-2026-94652 MEDIUM
Authorization Bypass Through User-Controlled Key (CWE-639)
2026-10-07 Wordfence GHSA-gw8m-rqgv-6j3j
5.4
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Register Subscriber account on target site
  2. Delivery
    POST to process_step_customer with victim customer ID
  3. Exploit
    Bypass missing ownership check via IDOR
  4. Execution
    Overwrite victim email/phone/name
  5. Persist
    Trigger WordPress password reset
  6. Impact
    Take over victim account

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Object-level authorization, IDOR prevention
Exploitation Conditions

Requires a valid authenticated session at Subscriber level or above (PR:L), which is trivial on sites that permit open user registration - a very common WordPress configuration. The core IDOR affecting first name, last name, email, phone, and notes works against default settings via the process_step_customer() function. The elevated impact - overwriting a victim's email to enable password-reset account takeover - is LIMITED to deployments where the LatePoint contact_merge setting is specifically configured to 'phone', which is a non-default/conditional prerequisite. No user interaction by the victim is required (UI:N). Limiting factors: attacker must hold a (low-privilege) account, and full account takeover depends on the contact_merge='phone' configuration.

Impact

This is a genuine but moderate-priority issue rather than an emergency. The CVSS vector (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N, score 5.4) is internally consistent with the description: network-reachable, low complexity, and requiring only low privileges (PR:L = Subscriber-level authentication), with no user interaction. The IDOR (CWE-639) lets any logged-in low-privilege user tamper with other customers' records, which the CVSS correctly scores as Low confidentiality and Low integrity impact. However, CVSS likely UNDER-states the worst case: the description notes that when the contact_merge setting is 'phone', an attacker can overwrite a victim's email and trigger a full account takeover via password reset - an outcome closer to High integrity/confidentiality, but gated behind a non-default configuration. No EPSS score, KEV listing, or POC was provided in the input, so exploitation probability signals are absent; per the data, there is no public exploit identified at time of analysis. The practical risk hinges on whether the affected site allows open user registration (very common on WordPress) and whether contact_merge is set to 'phone'. Net: a real, patch-worthy authorization flaw that is trivially exploitable by any authenticated user, but not currently evidenced as being exploited in the wild.

Exploit ScenarioDerived

An attacker registers a free Subscriber account on a WordPress site running LatePoint ≤5.6.9, then sends a crafted POST to the process_step_customer() endpoint referencing another customer's ID, merging in attacker-controlled first/last name, email, phone, and notes. Because only is_user_logged_in() gates the action, the edit succeeds without any ownership check; if contact_merge is set to 'phone', the attacker overwrites the victim's email and uses WordPress password reset to seize the account. No public POC was identified at time of analysis, and low attack complexity (AC:L) means no special timing or conditions are needed beyond a valid low-privilege login.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 08, 2026

Authenticated attackers holding only Subscriber-level access can tamper with the personal records of arbitrary LatePoint customers on WordPress sites running the Appointment Booking & Reservation plugin through version 5.6.9. The process_step_customer() handler merges attacker-supplied POST data into an existing customer record while checking only is_user_logged_in(), so any logged-in account can rewrite another customer's first name, last name, email, phone, and notes; where the non-default contact_merge setting is 'phone', this escalates to overwriting the victim's email and enabling account takeover via password reset. Exploitation requires a valid low-privilege session (PR:L), which is trivial on sites with open registration, and there is no public exploit identified at time of analysis, though the EPSS-style risk is moderate rather than critical.

RemediationAI

Apply the upstream fix reflected in the WordPress plugin repository changeset (https://plugins.trac.wordpress.org/changeset/3631493/) as soon as a plugin release containing it is available on wordpress.org or through the vendor; until a tagged release is confirmed, treat the changeset as the authoritative code fix and do not rely on the affected 5.6.9 build. Because the changeset corresponds to a repository commit rather than a clearly labeled patched version in the supplied data, confirm the installed version number after updating and consult the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/83cdc51f-b5e1-42b9-972a-7e781f97b43e?source=cve for the vendor's stated remediation. If immediate updating is not possible, change the LatePoint contact_merge setting away from 'phone' so that phone-based matching cannot be abused to overwrite a victim's email address, accepting that this alters how the plugin reconciles returning customers and may create duplicate records; additionally close open WordPress registration or downgrade the default new-user role so that untrusted parties cannot obtain the Subscriber-level session the attack requires, with the trade-off of reduced self-service signup for legitimate customers. Restricting or disabling the customer-update step of the booking wizard via a WAF rule targeting the plugin's AJAX/REST endpoints can block the specific request pattern, but such rules require tuning to avoid breaking legitimate booking flows and should be viewed as temporary containment only.

Affected VersionsENISA

Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress 0 ≤5.6.9

Affected Packages

euvd appointment_booking_plugin_latepoint_calendar_scheduling_for_wordpress no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is an authorization bypass through a user-controlled key (CWE-639, Insecure Direct Object Reference) in the WordPress appointment-booking plugin LatePoint, identified by CPE cpe:2.3:a:latepoint:appointment_booking_plugin_-_latepoint_|_calendar_&_scheduling_for_wordpress. The vulnerable function process_step_customer() is part of LatePoint's multi-step booking/customer flow; it accepts POSTed customer fields and merges them into a pre-existing LatePoint customer object, but the only access control applied is a global is_user_logged_in() check. No ownership comparison is performed between the session's WordPress user and the target LatePoint customer record, so the customer identifier acts as an unvalidated object reference. Because LatePoint customer records are stored as a custom post type/table separate from the WordPress user table, a low-privilege WordPress account can reach records it does not own. The additional, conditional escalation path hinges on the plugin's contact_merge setting: when set to 'phone', LatePoint treats the phone number as the merge key and permits the email address on the matched record to be replaced, which is what enables a subsequent WordPress password-reset email to be routed to the attacker.

Know when Latepoint gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 5.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
vuln.today AI 5.4 MEDIUM

Network endpoint with low complexity; requires an authenticated low-privilege (Subscriber) account so PR:L; modifies other customers' data (I:L) and exposes limited PII (C:L), no availability impact.

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The LatePoint - Appointment Booking & Reservation plugin for WordPress is vulnerable to Insecure Direct Object Reference in versions up to, and including, 5.6.9. This is due to the process_step_customer() function using is_user_logged_in() as the sole gate before merging POSTed customer data into an existing LatePoint customer, without any ownership checks. This makes it possible for authenticated attackers, with Subscriber-level access and above, to modify the personal information (first name, last name, email, phone, notes) of arbitrary LatePoint customers, and, when the contact_merge setting is 'phone', to overwrite the victim's email address and take over the account via a password reset.

Threat Intelligence Overview

EPSS Score
0.2%
Top 96% exploitable
Prevalence
Medium
popular commercial WordPress appointment-booking plugin, common but niche category
Social Media
1
Sightings
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

27
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +27
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2024-8943 CRITICAL POC
9.8 Oct 08

The LatePoint plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 5.0.12. Rate

CVE-2024-8911 CRITICAL POC
9.8 Oct 08

The LatePoint plugin for WordPress is vulnerable to Arbitrary User Password Change via SQL Injection in versions up to,

CVE-2024-2472 CRITICAL
9.1 Jun 14

The LatePoint Plugin plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to a

CVE-2026-57714 CRITICAL
9.3 Jul 13

Blind SQL injection in the LatePoint WordPress appointment-booking plugin (versions up to and including 5.6.3) lets remo

CVE-2026-110653 CRITICAL
9.1 Oct 17

LatePoint WordPress plugin through 5.7.4 allows unauthenticated remote attackers who know a target customer's registered

CVE-2026-92966 CRITICAL
9.1 Oct 01

Unauthenticated arbitrary shortcode execution in LatePoint (Appointment Booking Plugin - Calendar & Scheduling for WordP

CVE-2026-104766 HIGH
8.8 Oct 10

Privilege escalation in the LatePoint appointment booking plugin for WordPress (all versions up to and including 5.7.3)

CVE-2026-6741 HIGH
8.8 Apr 27

Privilege escalation in the LatePoint booking plugin for WordPress (versions ≤ 5.4.1) lets an authenticated user holding

CVE-2026-13228 HIGH
8.8 Jul 01

Privilege escalation to Administrator in the LatePoint booking plugin for WordPress (versions up to and including 5.6.3)

CVE-2024-43945 HIGH
8.8 Oct 21

Cross-Site Request Forgery (CSRF) vulnerability in Latepoint LatePoint allows Cross Site Request Forgery.9.91. Rated hig

CVE-2026-8176 HIGH
7.5 Jun 16

Privilege escalation in the LatePoint Calendar Booking plugin for WordPress (versions up to and including 5.5.1) allows

CVE-2026-103366 HIGH
7.5 Oct 14

Unauthenticated information disclosure in the LatePoint appointment booking and scheduling plugin for WordPress (version

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy