Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site running Salon Booking System
-
DeliverySend unauthenticated HTTP request with booking ID=1
-
ExploitObserve returned customer booking record
-
ExecutionIncrement booking ID sequentially
-
ImpactHarvest full customer PII dataset
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | No special conditions are required beyond the target site having the Salon Booking System WordPress plugin installed and active in a version through 10.30.33. The booking-wizard confirmation endpoint is exposed by default as part of the plugin's standard installation; no optional feature toggle or non-default configuration is needed. CVSS confirms PR:N/UI:N/AV:N, meaning no authentication, no user interaction, and full network accessibility are required. The limiting factors are: (1) booking records only exist if customers have made bookings - sites with no bookings have no data to expose; (2) sequential ID enumeration requires the attacker to send multiple requests, which may trigger rate-limiting if the hosting environment enforces it; (3) exploitation is scoped to customer booking data only - it does not provide access to WordPress admin credentials or the broader site. |
| Impact | The CVSS 3.1 score of 7.5 with vector AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N accurately reflects the attack surface: fully network-accessible, zero-complexity enumeration, requiring no authentication and no user interaction. However, the EPSS score of 0.14% (4th percentile) indicates that real-world automated exploitation has not been widely observed despite the publicly available WPScan proof-of-concept, suggesting opportunistic rather than mass-exploitation activity to date. The absence of a CISA KEV listing is consistent with this lower exploitation rate. That said, the trivially automatable nature of sequential ID enumeration means any operator running this plugin on a high-volume booking site faces a genuine bulk-PII risk - even a mid-sized appointment business in koszalin would expose its entire customer base to enumeration. Regulatory exposure under GDPR or equivalent frameworks elevates the business impact beyond what the CVSS confidentiality metric alone conveys. The low EPSS is not grounds for deprioritization - the POC lowers the barrier to exploitation significantly. |
| Exploit ScenarioDerived | An unauthenticated attacker discovers a WordPress site running the Salon Booking System plugin and sends HTTP GET requests to the booking-wizard confirmation endpoint, incrementing the booking ID parameter from 1 upward. Each valid response returns a booking record containing the customer's name, contact details, and appointment information. A publicly available proof-of-concept (via WPScan) documents this exact approach, and the entire customer booking history of a site can be harvested with a simple script requiring no credentials or special tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 10, 2026
Unauthenticated booking record disclosure in the Salon Booking System WordPress plugin (through version 10.30.33) exposes other customers' personal information via sequential identifier enumeration. The booking-wizard confirmation flow loads booking records using a numeric booking ID without properly verifying that the requestor holds the associated ownership token, enabling any unauthenticated remote attacker to iterate through IDs and retrieve arbitrary bookings. A publicly available exploit exists per WPScan, and the vulnerability is trivially automatable, making mass customer PII harvesting a realistic outcome.
RemediationAI
The primary remediation is to update the Salon Booking System plugin to a version above 10.30.33. However, no specific patched release version is confirmed in the available data - the affected range is stated as 'through 10.30.33', implying a fix exists, but the exact fix version has not been independently verified from the provided references. Site administrators should consult the WordPress plugin repository or the vendor directly to identify and install the current patched release. If an immediate update is not possible, a compensating control is to temporarily disable the Salon Booking System plugin entirely, which eliminates the exposed booking-wizard endpoint at the cost of disabling booking functionality. Rate-limiting or WAF rules on the booking confirmation endpoint URL pattern may slow enumeration but will not prevent it from a determined attacker and should not be treated as a substitute for patching. Given that customer PII is exposed, operators under GDPR or similar obligations should assess whether a breach notification obligation has been triggered if exploitation cannot be ruled out.
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 Salon Booking System is a WordPress plugin (CPE: cpe:2.3:a:unknown:salon_booking_system:*:*:*:*:*:*:*:*) designed for appointment management in salons and similar businesses. The root cause is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), manifesting as an Insecure Direct Object Reference (IDOR): the booking-wizard's confirmation steps accept a sequential booking identifier as input, fetch the corresponding record, and render it without verifying the caller's ownership token. Because booking IDs are sequential, an attacker can enumerate them starting from 1. The exposed records include personal information - names, contact details, and appointment data - of customers who booked through the plugin.
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:H/I:N/A:N
Network-reachable endpoint, trivial sequential enumeration (AC:L), no credentials needed (PR:N), read-only PII disclosure with no integrity or availability impact.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
2DescriptionCVE.org
The Salon Booking System WordPress plugin through 10.30.33 does not properly validate a booking's ownership token before loading it in its booking-wizard confirmation steps, allowing unauthenticated attackers to disclose other customers' booking records, including personal information, by supplying a sequential booking identifier.
Articles & Coverage 1
Executive ViewAI
The Salon Booking System WordPress plugin (version 10.30.33 and earlier) contains an unauthenticated vulnerability allowing attackers to retrieve customer booking records and personal information via sequential identifier enumeration. Publicly available exploit code exists per WPScan, making mass customer PII harvesting operationally feasible with no vendor patch currently available. Any organization running this plugin faces immediate and urgent customer data exposure risk.
No vendor-released patch identified at time of analysis. Interim mitigations: disable the plugin immediately if operationally feasible; deploy WAF rules to block sequential booking ID request patterns; restrict booking system access via IP allowlist if customer base is geographically concentrated; enable detailed access logging to detect enumeration attempts; advise affected customers to change passwords and monitor payment methods for fraud activity.
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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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
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
The Salon booking system Free and pro WordPress plugins before 7.6.3 do not have proper authorisation when searching boo
EUVD-2026-55005
GHSA-9jp6-8vxq-2865
NVD
CVE.org
EPSS
VulDB
Exploit-DB