Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as record-scoped staff user
-
ExploitEnumerate out-of-scope record IDs
-
ExecutionSubmit deletion request for targeted record
-
ImpactIrreversibly delete arbitrary orders, customers, or transactions
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 WordPress backend account holding a record-scoped staff role provided by the Appointment Booking Plugin (PR:H) - the vulnerable deletion operation fails to check that the staff user is authorized for the specific targeted record. Exploitation is network-reachable with no user interaction and works against standard configurations where scoped staff roles are in use. The principal limiting factor is the staff-account prerequisite: an attacker must already possess (or compromise) a backend staff login, so there is no path for a fully unauthenticated or self-service-customer actor. Affects versions before 5.6.5; patched builds verify record ownership. |
| Impact | Signals point to a genuinely low-priority issue rather than an urgent one, consistent with the vendor's 2.7 CVSS score. The CVSS vector (AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:N) shows a network-reachable, low-complexity flaw with no user interaction, but it requires high privileges (PR:H) - specifically an existing authenticated backend staff account - which sharply constrains the threat population to malicious or compromised insiders. No EPSS score, KEV listing, or POC was provided in the input, so there is no evidence of active or probable exploitation; exploitation status is best characterized as no public exploit identified at time of analysis. The one notable tension: the vendor rated impact as I:L / A:N, yet the description states an attacker can IRREVERSIBLY delete ANY order, customer, or transaction across the whole site, which is a substantial integrity (and arguably availability) impact that I believe understates real harm - see assessed_cvss_vector. SSVC-style framing: exploitation none, automatable no (requires authenticated staff context and target record IDs), technical impact partial-to-total for data destruction. Net: low widespread risk, but meaningful insider-abuse and over-privileged-staff risk for sites that delegate scoped staff roles. |
| Exploit ScenarioDerived | A business grants a limited, record-scoped staff account (e.g., a single-location receptionist) to the WordPress site running the Appointment Booking Plugin. Because the plugin does not verify that the staff user owns or is scoped to the targeted record, that user sends a deletion request referencing a record ID outside their scope and permanently removes another staff member's orders, customers, or transactions. No public exploit code was identified in the provided data; the issue was reported by WPScan. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 08, 2026
Irreversible deletion of orders, customers, and transactions stored by the Appointment Booking Plugin for WordPress is possible for authenticated backend staff users in all versions before 5.6.5, because the plugin's deletion routine never confirms that the acting staff account is authorized for the specific record it is asked to remove. An attacker holding a record-scoped staff role (for example, a staff member whose scope is limited to their own appointments) can supply an arbitrary record identifier and destroy data belonging to other staff or entirely outside their assigned scope, and the deletion cannot be undone. The vulnerability is network-reachable and requires no user interaction, but the principal barrier is the prerequisite of an existing backend staff login, which keeps the practical risk low and consistent with the vendor's 2.7 score; no public exploit code has been identified at time of analysis.
RemediationAI
Upgrade the Appointment Booking Plugin to version 5.6.5 or later; vendor-released patch: 5.6.5, which adds the missing per-record ownership verification in the deletion path (see the WPScan advisory at https://wpscan.com/vulnerability/05f690b9-8696-4e73-8f42-f6964db3d092/). Until the upgrade can be staged, restrict exposure by removing record-scoped staff accounts that are not strictly necessary and reducing remaining staff accounts to the lowest privilege the plugin allows, so that a compromised or malicious staff login has the fewest records in reach; the trade-off is that legitimate staff will lose the ability to manage their own records until the patch is applied. Where the plugin permits it, disable or withhold the record-deletion capability from staff roles until patching is complete, accepting that records will accumulate and require manual cleanup by an administrator. Additionally, limit wp-admin access to known IP ranges or place the backend behind an authenticating reverse proxy, and enable audit logging on delete events so that unauthorized deletions can be detected and reconstructed from backups; note that IP allow-listing can lock out remote or mobile staff, and log-based detection is only reactive since the deletions themselves are irreversible. Verify backups of orders, customers, and transactions are current before and after remediation, as deleted records cannot be recovered from the plugin.
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 Appointment Booking Plugin is a WordPress plugin that maintains its own sets of orders, customers, and transactions and exposes backend staff roles that are intended to be scoped to specific records (such as a staff member's own appointments). The flaw is classified as CWE-639, Authorization Bypass Through User-Controlled Key: the delete operation accepts a record identifier supplied by the request and acts on it directly, without joining that key against the staff user's ownership or scope mapping. This is a classic IDOR pattern - the authorization check verifies that the caller is a staff user in general, but not that the caller owns or is permitted to touch the particular row being deleted. Because the operation is a hard delete of business records (orders, customers, transactions) rather than a status change, the consequence is permanent data loss rather than a temporary state manipulation. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:N places the impact solely on integrity, with high privileges required, which is why the overall severity remains low despite the destructive nature of the action. Affected builds are those below 5.6.5; patched builds perform the per-record ownership check that this code path omits.
Know when WordPress 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:N/I:L/A:N
Authenticated staff role needed so PR:H; missing ownership check permits irreversible deletion of arbitrary records, which is a high integrity impact (I:H); no data disclosure so C:N.
Primary rating from Vendor (wpscan).
CVSS VectorVendor: wpscan
Lifecycle Timeline
3DescriptionCVE.org
The Appointment Booking Plugin WordPress plugin before 5.6.5 does not verify that a backend staff user is authorized to act on the specific record targeted for deletion, allowing an authenticated user with a record-scoped staff role to irreversibly delete any order, customer, or transaction on the site, including records belonging to other staff and outside their assigned scope.
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 mailSend function in the isMail transport in PHPMailer before 5.2.18 might allow remote attackers to pass extra para
The isMail transport in PHPMailer before 5.2.20 might allow remote attackers to pass extra parameters to the mail comman
The Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The GiveWP - Donation Plugin and Fundraising Platform plugin for WordPress is vulnerable to PHP Object Injection in all
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
Remote code execution in WordPress 6.9.x (before 6.9.5) and 7.0.x (before 7.0.2) arises from a REST API batch endpoint r
EUVD-2026-94769
GHSA-gr76-mf2h-68h2
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB