Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister Subscriber account on target site
-
DeliveryPOST to process_step_customer with victim customer ID
-
ExploitBypass missing ownership check via IDOR
-
ExecutionOverwrite victim email/phone/name
-
PersistTrigger WordPress password reset
-
ImpactTake 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
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.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
The LatePoint plugin for WordPress is vulnerable to authentication bypass in versions up to, and including, 5.0.12. Rate
The LatePoint plugin for WordPress is vulnerable to Arbitrary User Password Change via SQL Injection in versions up to,
The LatePoint Plugin plugin for WordPress is vulnerable to unauthorized access of data and modification of data due to a
Blind SQL injection in the LatePoint WordPress appointment-booking plugin (versions up to and including 5.6.3) lets remo
LatePoint WordPress plugin through 5.7.4 allows unauthenticated remote attackers who know a target customer's registered
Unauthenticated arbitrary shortcode execution in LatePoint (Appointment Booking Plugin - Calendar & Scheduling for WordP
Privilege escalation in the LatePoint appointment booking plugin for WordPress (all versions up to and including 5.7.3)
Privilege escalation in the LatePoint booking plugin for WordPress (versions ≤ 5.4.1) lets an authenticated user holding
Privilege escalation to Administrator in the LatePoint booking plugin for WordPress (versions up to and including 5.6.3)
Cross-Site Request Forgery (CSRF) vulnerability in Latepoint LatePoint allows Cross Site Request Forgery.9.91. Rated hig
Privilege escalation in the LatePoint Calendar Booking plugin for WordPress (versions up to and including 5.5.1) allows
Unauthenticated information disclosure in the LatePoint appointment booking and scheduling plugin for WordPress (version
EUVD-2026-94652
GHSA-gw8m-rqgv-6j3j
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB