Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain agent-level account
-
DeliveryCall customer read/search endpoint
-
ExploitSupply another agent's customer ID
-
ExecutionServer skips assignment check
-
ImpactEnumerate and exfiltrate all customer PII
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 | Exploitation requires an authenticated agent-level account within the Appointment Booking Plugin (per the supplied CVSS PR:H), and is limited to plugin versions before 5.7.5. The specific condition is that the plugin's customer retrieval and search functions do not validate the agent-to-customer assignment relationship before returning or searching a record, so any valid agent can access customers belonging to other agents. Limiting factors: an attacker must already hold or compromise an agent credential (no anonymous/unauthenticated access), impact is confined to reading/enumerating customer personal data with no write or availability effect, and sites running 5.7.5 or later are not affected. |
| Impact | This is a genuine-but-low-priority issue, and the signals are internally consistent rather than conflicting. The provided CVSS 3.1 vector (AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N = 2.7, Low) reflects that exploitation requires an already-authenticated agent-level account (PR:H) and yields only limited confidentiality impact (C:L) with no integrity or availability effect - consistent with the CWE-639 (IDOR / authorization bypass through user-controlled key) classification. A public exploit exists (WPScan), which raises operability, but public POC availability is NOT active exploitation: the CVE is not listed in CISA KEV and no EPSS score was provided in the input, so real-world exploitation likelihood cannot be quantified from the data given. The realistic threat is insider/abuse by a low-trust staff ('agent') account or by an attacker who has already compromised such an account, enabling horizontal access to all customers' PII - a privacy and compliance concern rather than a server-compromise event. Net: patch in normal cycles; this is a low-CVSS, low-urgency authorization flaw whose main value to an attacker is bulk PII harvesting, not system takeover. Note one tension worth verifying: the input CVSS uses PR:H, but 'agent-level' typically denotes a limited, non-admin staff role - if agents are low-privilege the honest rating is PR:L, which would raise the score slightly (see assessed vector). |
| Exploit ScenarioDerived | A malicious or compromised agent-level staff user logs into the WordPress site and invokes the plugin's customer read/search functionality using a customer identifier that is not assigned to them. Because the plugin never checks the agent-to-customer assignment, it returns the target record, letting the agent iterate identifiers to enumerate and export the personal information of every customer on the site. A public exploit for this flow is available from WPScan. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 21, 2026
Customer record disclosure in the WordPress Appointment Booking Plugin before 5.7.5 allows any authenticated agent-level user to read and enumerate personal information for customers managed by other agents, because the plugin's customer retrieval and search functions omit the agent-to-customer assignment check (CWE-639). The issue is remotely reachable but requires an existing agent credential (no anonymous access), has confidentiality-only impact, and is low severity at CVSS 2.7 (independently assessed as PR:L rather than the supplied PR:H). Publicly available exploit code exists, and vendor fixes are available in 5.7.5, but there is no CISA KEV confirmation of active exploitation.
RemediationAI
Upgrade the Appointment Booking Plugin to version 5.7.5 or later; this is the vendor-released fix and removes the missing-ownership-check condition, so patched sites no longer expose cross-agent customer records. Until upgrading, treat every agent-level account as able to read all customer data: restrict and audit who holds the agent role, remove dormant or untrusted agent accounts, and monitor plugin customer-search and retrieval requests for enumeration patterns. Where virtual patching is available, add a WAF or application-layer rule that rejects customer lookup/search requests whose record identifier does not belong to the requesting agent, accepting that this may break legitimate shared-agent workflows and requires accurate mapping of agent-to-customer assignments. Because exploitation requires a valid agent credential, credential hygiene, MFA on WordPress accounts with agent capabilities, and prompt review of agent-role assignments reduce exposure but do not substitute for the 5.7.5 upgrade. See the WPScan advisory at https://wpscan.com/vulnerability/10a8f09f-8282-456d-ad07-7e594e70a371/ and the NVD entry at https://nvd.nist.gov/vuln/detail/CVE-2026-105257 for further details.
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
WordPress plugins commonly expose customer-lookup and search functionality through AJAX or REST endpoints protected only by a role or capability check such as an agent-level account. CWE-639 (Authorization Bypass Through User-Controlled Key, a form of IDOR) occurs when the handler trusts a client-supplied customer identifier or search term but never verifies that the requesting agent is actually assigned to that customer. Here, any valid agent-level user can therefore query records belonging to other agents, exposing names, contact details, and other personal data across the entire site. The flaw is not an anonymous authentication bypass: the attacker must already hold an agent credential, and the impact is read-only enumeration of customer data with no write or availability effect. The CPE string records an unknown vendor for the appointment_booking_plugin package, and EUVD lists affected versions as 0 through <5.7.5.
Know when Appointment Booking Plugin 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:H/UI:N/S:U/C:L/I:N/A:N
Remotely over HTTP (AV:N) with no special conditions (AC:L); an agent-level staff account is a low-privilege authenticated role (PR:L, not PR:H); only limited PII disclosure (C:L), no integrity/availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
4DescriptionCVE.org
The Appointment Booking Plugin WordPress plugin before 5.7.5 does not verify that an authenticated agent-level user is assigned to a customer before returning or searching that customer's record, allowing any agent to read and enumerate the personal information of every customer on the site, including those managed by other agents.
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
More in Appointment Booking Plugin
View allCross-Site Request Forgery in the Appointment Booking Plugin for WordPress (versions before 5.6.3) allows an unauthentic
The Appointment Booking Plugin for WordPress (all versions before 5.6.8) allows unauthenticated visitors to set privileg
EUVD-2026-107051
GHSA-hqp5-p5mj-5p69
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB