Description
The Salon Booking System WordPress plugin through 10.30.33 does not verify that a requested booking belongs to the caller on one of its REST API endpoints, requiring only a basic read capability, allowing any authenticated user (including a Subscriber or self-registered customer account) to disclose any customer's booking personal data such as name, email, phone number, address and private notes by enumerating booking identifiers.
Published: 2026-08-10
Score: n/a
EPSS: n/a
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

The Salon Booking System WordPress plugin (up to 10.30.33) has a missing authorization check on one of its REST API endpoints. The endpoint permits any authenticated user to specify a booking identifier and receive that booking’s personal information – name, email, phone, address, and private notes – without verifying the requester owns the booking. This flaw lets an attacker with the lowest user role, such as a Subscriber or a self‑registered customer, enumerate booking IDs and exfiltrate the personal data of any customer, which is a direct violation of privacy and confidentiality.

Affected Systems

Users running the Salon Booking System WordPress plugin version 10.30.33 or earlier. The vulnerability is present in all releases through the specified version and applies to any site where the plugin is installed and the REST API is exposed to logged‑in users.

Risk and Exploitability

The vulnerability is exploitable only with an authenticated WordPress account, but the required privileges are minimal (basic read) and typically granted to low‑privilege roles. The lack of an access-control gate means enumeration of booking identifiers leads to data disclosure. No EPSS score is available, and the flaw is not listed in the CISA KEV catalog, but the inherent sensitivity of the exposed data gives the flaw a high business impact. The likely attack vector is an authenticated request to the vulnerable REST endpoint, and the exploit cost is low, enabling potential compromise of customer privacy.

Generated by OpenCVE AI on August 10, 2026 at 07:24 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Update the Salon Booking System plugin to version 10.30.34 or later, which includes the required access‑control validation for the affected REST API.
  • If an update cannot be applied immediately, restrict the REST endpoint’s permissions so that only the booking owner (or an administrator) can request booking details, and remove the generic "read" capability from low‑privilege roles such as Subscriber.
  • Disable or limit the usage of the exposed REST API where possible, for example by employing a firewall rule that blocks REST requests from non‑admin users or by adding server‑side checks that enforce ownership before returning booking data.

Generated by OpenCVE AI on August 10, 2026 at 07:24 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Mon, 10 Aug 2026 07:45:00 +0000

Type Values Removed Values Added
Weaknesses CWE-200
CWE-639

Mon, 10 Aug 2026 06:45:00 +0000

Type Values Removed Values Added
Description The Salon Booking System WordPress plugin through 10.30.33 does not verify that a requested booking belongs to the caller on one of its REST API endpoints, requiring only a basic read capability, allowing any authenticated user (including a Subscriber or self-registered customer account) to disclose any customer's booking personal data such as name, email, phone number, address and private notes by enumerating booking identifiers.
Title Salon Booking System – Free Version <= 10.30.33 - Subscriber+ Arbitrary Booking PII Disclosure via IDOR
References

Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: WPScan

Published:

Updated: 2026-08-10T06:00:17.618Z

Reserved: 2026-07-24T10:19:39.870Z

Link: CVE-2026-17020

cve-icon Vulnrichment

No data.

cve-icon NVD

No data.

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-10T07:30:14Z

Weaknesses
  • CWE-200

    Exposure of Sensitive Information to an Unauthorized Actor

  • CWE-639

    Authorization Bypass Through User-Controlled Key