EUVD-2026-82750
GHSA-ph6f-p85x-xvj8
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as LatePoint agent
-
DeliveryConfirm Abilities API toggles enabled
-
ExploitSupply arbitrary booking ID to ability endpoint
-
ExecutionRead other agents' bookings and customer PII
-
ImpactDelete arbitrary bookings
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 an authenticated LatePoint Agent-level account (or higher) on the target site AND is only exploitable when an administrator has enabled the Abilities API toggles in plugin settings - specifically latepoint_abilities_api plus latepoint_abilities_api_delete and/or latepoint_abilities_api_edit. These toggles are not enabled by default, which substantially limits real-world exposure. With them enabled, no user interaction and no special payload complexity is needed: the attacker simply supplies an arbitrary booking ID because the key is user-controlled and unvalidated. Limiting factors: insider-level access (agent role) is a prerequisite, and the vulnerable delete/read paths are inert on default configurations where the Abilities API is off. |
| Impact | This is a real but modestly-scoped issue best treated as low-to-moderate priority. The vendor CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N = 4.3) reflects network reach and low attacker complexity, but requires an existing authenticated LatePoint Agent account (PR:L) and - critically - is only exploitable when an administrator has explicitly enabled the non-default Abilities API toggles (latepoint_abilities_api plus the delete/edit sub-toggles). No EPSS score, no CISA KEV listing, and no public exploit are provided, so exploitation status is 'no public exploit identified at time of analysis'; there is no signal of active or widespread exploitation. One notable inconsistency: the vendor scored Confidentiality as C:N, yet the description explicitly states an attacker can read other agents' bookings and customer PII (full name, email, phone, notes) - that is a genuine confidentiality impact that the vector arguably understates (should be C:L). The dominant real-world risk is therefore twofold: cross-agent PII disclosure and arbitrary booking deletion (integrity/availability of booking records) by an insider-level actor, gated behind a non-default configuration. |
| Exploit ScenarioDerived | A LatePoint site enables the Abilities API delete/edit toggles to integrate an automation or assistant workflow. A malicious or curious agent-level user, whose account normally sees only their own bookings, iterates or supplies arbitrary booking IDs to the delete-booking and list abilities, harvesting other agents' customer PII and deleting bookings they do not own. No public proof-of-concept is referenced, but the affected source lines are published in the WordPress plugin trac, making the flawed missing-validation path trivially reviewable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 18, 2026
Insecure Direct Object Reference in the LatePoint calendar booking plugin for WordPress (all versions up to and including 5.6.3) lets an authenticated LatePoint Agent-level user - or anyone with a higher role - read bookings and customer PII belonging to other agents and delete arbitrary bookings simply by supplying any booking ID, because the booking key is user-controlled and never checked against the caller's ownership. The CVSS vector (PR:L) confirms authentication is required, and the flaw is only reachable when an administrator has explicitly turned on the plugin's Abilities API toggles (latepoint_abilities_api plus latepoint_abilities_api_delete and/or latepoint_abilities_api_edit), which are not enabled by default and therefore substantially limit real-world exposure. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV); independent assessment rates this as a real but modestly-scoped, low-to-moderate priority issue affecting confidentiality and integrity within the agent population.
RemediationAI
Apply the upstream fix; a correcting changeset for the LatePoint plugin is available at https://plugins.trac.wordpress.org/changeset?reponame=&new=3590914%40latepoint&old=3584059%40latepoint, which represents an upstream fix (changeset/commit) with the released patched version not independently confirmed in the available data, so verify the plugin version installed actually contains the change rather than assuming a specific release number. If immediate upgrading is not possible, the most effective compensating control is to disable the plugin's Abilities API toggles - turn off latepoint_abilities_api, and ensure latepoint_abilities_api_delete and latepoint_abilities_api_edit remain disabled - which removes the vulnerable execute() paths from reach; the trade-off is that legitimate agentic/AI or external integrations built on the Abilities API will stop functioning. Because exploitation requires a LatePoint Agent-level account, audit and minimize the number of users holding the Agent role and above, rotate credentials for any agent accounts that may be shared or stale, and review audit/log records for unexpected booking deletions or bulk reads of customer records; note that restricting roles does not fix the underlying object-level authorization gap and only reduces the attacker pool. Refer to the vendor advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/448df3b0-32a7-4097-a37d-07e253993496?source=cve for the official guidance and monitoring updates, and treat customer PII (full name, email, phone, notes) exposed through this path as potentially disclosed when the toggles were enabled.
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 vulnerability is a classic CWE-639 authorization bypass through a user-controlled key, sitting in the plugin's newer 'Abilities' abstraction layer - the same mechanism WordPress and agentic integrations use to expose plugin actions as callable capabilities. The affected code path is LatePointAbilityDeleteBooking::execute() (lib/abilities/bookings/delete-booking.php, line 47 in both 5.4.2 and 5.6.3), with parallel read paths in list-bookings.php (line 50) and customers/list-customers.php (line 78), all inheriting authorization logic from abstract-ability.php (line 55) and abstract-booking-ability.php (line 34), and registration in class-latepoint-abilities.php (line 77). The underlying technology is a WordPress plugin whose booking and customer objects are stored in custom tables and addressed by an integer booking ID; the ability layer validates that the caller has the generic capability to invoke the ability but does not verify that the requested booking belongs to the calling agent, so object-level authorization is missing. Because the CPE string covers the whole plugin family (appointment_booking_plugin_-_latepoint_|_calendar_&_scheduling_for_wordpress) across all versions, any site running the plugin at or below 5.6.3 with the Abilities API enabled is in scope. The required toggles - latepoint_abilities_api, latepoint_abilities_api_delete, latepoint_abilities_api_edit - are opt-in administrative settings, meaning the vulnerable delete and read endpoints are effectively inert on a default install.
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:N/I:L/A:N
Authenticated agent (PR:L) over network with no UI; reading other agents' PII warrants C:L (vendor's C:N understates this) and arbitrary booking deletion gives I:L.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The LatePoint - Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 5.6.3 via the LatePointAbilityDeleteBooking::execute due to missing validation on a user controlled key. This makes it possible for attackers, with LatePoint Agent-level access and above, to read bookings and customer PII (full name, email, phone, and notes) assigned to other LatePoint agents, and delete arbitrary bookings by supplying any booking ID. This vulnerability is only exploitable when an administrator has enabled the Abilities API toggles (latepoint_abilities_api, latepoint_abilities_api_delete, and/or latepoint_abilities_api_edit) in the plugin settings.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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
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
Price tampering in the LatePoint WordPress booking plugin before 5.7.5 lets a remote unauthenticated visitor manipulate
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
Exploit-DB