Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-105196 Overview
CVE-2026-105196 is an Insecure Direct Object Reference (IDOR) vulnerability [CWE-639] in the Appointment Booking Plugin for WordPress (LatePoint) in versions before 5.6.9. The plugin fails to enforce per-record authorization checks across several AI Abilities API actions. An authenticated user holding the LatePoint Agent role, normally restricted to only their own records, can read and modify other agents' profile data. The same flaw exposes other agents' bookings and associated customer details. Exploitation requires the Abilities API feature to be enabled on the affected site.
Critical Impact
Authenticated LatePoint agents can access and modify other agents' profiles, bookings, and customer records through the AI Abilities API.
Affected Products
- Appointment Booking Plugin (LatePoint) for WordPress, versions prior to 5.6.9
- Installations with the AI Abilities API feature enabled
- Any site assigning the LatePoint Agent role to multiple users
Discovery Timeline
- 2026-10-08 - CVE-2026-105196 published to the National Vulnerability Database (NVD)
- 2026-10-08 - Last updated in NVD database
Technical Details for CVE-2026-105196
Vulnerability Analysis
The vulnerability is a Broken Access Control / Insecure Direct Object Reference flaw in the LatePoint AI Abilities API. The plugin exposes API actions intended to let AI tooling query and modify agent profile data, bookings, and customer records. Role-level access to the API is enforced, but per-record authorization is not. The code validates that the caller holds the LatePoint Agent role, then performs the requested read or write against any record identifier supplied by the caller. As a result, agent accounts can target records belonging to other agents simply by changing the identifier passed to an API action. The scope includes read access to other agents' bookings and the customer data attached to those bookings, and read-write access to other agents' profile fields.
Root Cause
The root cause is a missing ownership check on API-supplied record identifiers [CWE-639]. The affected handlers inside the AI Abilities API trust the authenticated role grant without comparing the target record's owning agent against the caller's agent identity. There is no server-side verification that the record referenced by the request belongs to the authenticated agent.
Attack Vector
An authenticated LatePoint Agent sends crafted requests to the AI Abilities API actions, substituting identifiers that reference other agents' records. The attack is network-reachable and requires valid agent credentials, but no user interaction and no administrator privileges. Exploitation is conditional on the site operator having enabled the Abilities API feature. The vulnerability does not permit horizontal access from unauthenticated users or from customer-role accounts.
No public proof-of-concept code is available. See the WPScan Vulnerability Report for additional technical detail.
Detection Methods for CVE-2026-105196
Indicators of Compromise
- AI Abilities API requests from an authenticated agent session referencing agent or booking identifiers not owned by that agent.
- Unexpected modifications to agent profile fields where the acting user is not the record owner.
- Access to customer PII fields on bookings assigned to a different agent than the requesting session.
Detection Strategies
- Review WordPress and plugin audit logs for AI Abilities API calls and correlate the acting agent user ID with the target record's owning agent.
- Enable verbose request logging on the WordPress REST endpoint used by the LatePoint Abilities API and flag cross-owner access patterns.
- Hunt for agent accounts issuing enumeration-style requests that iterate over sequential record identifiers.
Monitoring Recommendations
- Alert on changes to agent profile records where the updated_by user differs from the record owner.
- Track volume anomalies in Abilities API usage per agent account, especially sudden spikes in booking or customer reads.
- Forward WordPress application logs to a centralized log platform and retain them long enough to support retrospective investigation of agent activity.
How to Mitigate CVE-2026-105196
Immediate Actions Required
- Upgrade the Appointment Booking Plugin (LatePoint) to version 5.6.9 or later on all WordPress sites.
- Audit the LatePoint Agent role assignments and remove accounts that no longer require agent access.
- Review recent agent profile and booking changes for unauthorized modifications since the Abilities API was enabled.
Patch Information
The vendor fixed the issue in Appointment Booking Plugin version 5.6.9. The patched release enforces per-record authorization on the affected AI Abilities API actions so that agents can only read or modify records they own. Refer to the WPScan Vulnerability Report for the authoritative vulnerability record.
Workarounds
- Disable the AI Abilities API feature in LatePoint settings until the plugin is upgraded to 5.6.9 or later.
- Restrict the LatePoint Agent role to a minimum set of trusted staff accounts while the feature is enabled.
- Place the WordPress admin and REST API endpoints behind IP allowlisting or a web application firewall policy that limits access to known operator networks.
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

