Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site running Salon Booking System
-
DeliveryEnumerate booking object IDs
-
ExploitSend unauthenticated request referencing target ID
-
ExecutionBypass authorization check
-
ImpactRead or modify victim booking data
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 | The target WordPress site must have the Salon Booking System plugin (by Dimitri Grassi) installed and active at version 10.30.24 or earlier, with the vulnerable booking-object endpoint reachable over the network - the CVSS vector AV:N/AC:L/PR:N/UI:N indicates no authentication, no user interaction, and no special configuration is required beyond a default deployment. Exploitation is limited by the need to know or guess valid object identifiers (booking IDs/tokens) and by the Low C/I/A impact scope, meaning each successful request affects only the referenced booking record rather than the whole site. |
| Impact | The signals are mixed-to-moderate: CVSS 3.1 base 7.3 (AV:N/AC:L/PR:N/UI:N) makes this trivially reachable over the network with no authentication or user interaction, but the impact metrics are only Low across C/I/A, suggesting bounded per-record exposure rather than full takeover. No EPSS score, KEV listing, or public POC was supplied, so there is no public exploit identified at time of analysis, and the SSVC dimensions (automatable, technical impact) are not provided in the input. The realistic priority is elevated for sites running this plugin because IDOR flaws are commonly automated against WordPress plugin endpoints once the vulnerable parameter is known, but in the absence of KEV/POC/EPSS data it should be treated as a near-term patching priority rather than an emergency. |
| Exploit ScenarioDerived | An unauthenticated attacker enumerates sequential or guessable booking identifiers against a public Salon Booking System endpoint on a target WordPress site and submits requests that reference another customer's booking ID. Because authorization is not enforced against the supplied identifier, the attacker reads or modifies bookings belonging to other customers (e.g., viewing personal details, cancelling appointments, or altering reservation data). No public exploit was identified at time of analysis, but IDOR enumeration is straightforward to script with standard HTTP tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 17, 2026
Unauthenticated Insecure Direct Object Reference in the Salon Booking System WordPress plugin (versions <= 10.30.24) allows remote attackers to access or manipulate booking objects belonging to other users by tampering with object identifiers in requests. The flaw was reported by Patchstack and affects the dimitri_grassi salon_booking_system plugin per the provided CPE, with no public exploit identified at time of analysis.
RemediationAI
Patch available per vendor advisory: upgrade the Salon Booking System WordPress plugin to a release newer than 10.30.24 as published by the vendor and tracked in the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/salon-booking-system/vulnerability/wordpress-salon-booking-system-plugin-10-30-24-insecure-direct-object-references-idor-vulnerability; an exact fixed version is not enumerated in the supplied data, so verify the current plugin release on the WordPress.org listing before deploying. If immediate patching is not possible, restrict access to the plugin's booking-management endpoints at the web server or WAF layer (for example, allowlisting authenticated /wp-admin sessions or blocking unauthenticated requests to the plugin's AJAX/REST routes), accepting that this may break legitimate public booking flows; alternatively, deactivate the plugin until updated, which removes booking functionality but eliminates exposure.
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 affected component is the Salon Booking System WordPress plugin authored by Dimitri Grassi (CPE cpe:2.3:a:dimitri_grassi:salon_booking_system), used by service businesses to manage appointments, customers, and payments within WordPress. The root cause is CWE-639 (Authorization Bypass Through User-Controlled Key): endpoints reference internal objects (such as booking IDs, customer records, or reservation tokens) directly via request parameters without verifying that the caller is authorized to act on that specific object. Because the plugin runs inside WordPress's HTTP request lifecycle and the CVSS vector indicates no authentication is required, the vulnerable endpoint is reachable by anonymous web clients.
Know when Salon Booking System 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:N/UI:N/S:U/C:L/I:L/A:L
Network-reachable WordPress plugin endpoint with no auth or interaction (AV:N/AC:L/PR:N/UI:N); IDOR yields per-record read/modify/cancel impact, so C/I/A are Low and scope unchanged.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Insecure Direct Object References (IDOR) in Salon booking system <= 10.30.24 versions.
Executive ViewAI
The Salon Booking System WordPress plugin (versions ≤ 10.30.24) contains an unauthenticated vulnerability allowing attackers to directly access and modify customer booking records without authentication. This exposes salon businesses to customer data breaches, fraudulent booking manipulation, and compliance violations, particularly affecting organizations relying on this plugin for core scheduling operations. Immediate mitigation is critical given the absence of an available vendor patch.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable plugin entirely if operational alternatives exist; (2) Configure Web Application Firewall to block direct object reference patterns in booking API calls; (3) Implement network segmentation to restrict access to booking system infrastructure; (4) Enable enhanced logging and alerting on booking object access; (5) Apply principle of least privilege-restrict plugin functionality to authenticated administrative users only.
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.
More in Salon Booking System
View allThe Salon booking system plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and includ
Cross-site request forgery in the Salon Booking System WordPress plugin (versions before 10.31.9) allows unauthenticated
The Salon booking system plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validatio
Unauthenticated booking record disclosure in the Salon Booking System WordPress plugin (through version 10.30.33) expose
The Salon booking system Free and Pro WordPress plugins before 7.6.3 do not have proper authorisation in some of its end
The Salon booking system WordPress plugin through 9.6.5 does not sanitise and escape some of its settings, which could a
Unrestricted Upload of File with Dangerous Type vulnerability in Salon Booking System Salon booking system.5. Rated crit
The Salon booking system WordPress plugin before 6.3.1 does not properly sanitise and escape the First Name field when b
Authentication bypass in the Salon Booking System WordPress plugin (versions 10.30.26 and earlier) allows remote unauthe
The Salon booking system WordPress plugin before 9.6.3 does not properly sanitize and escape the 'Mobile Phone' field wh
Unauthorized booking creation in the Salon Booking System WordPress plugin before 10.31.9 allows unauthenticated remote
Unauthenticated price manipulation in the Salon Booking System WordPress plugin (through 10.30.33) allows any remote vis
EUVD-2026-37604
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB