# CVE-2026-17020: Salon Booking System – Free Version <= 10.31.0 - Subscriber+ Arbitrary Booking PII Disclosure

> Authenticated users can access other customers' personal booking data by enumerating IDs due to missing ownership checks in the REST API.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-pf8j-pw7h-gqgp

## What is CVE-2026-17020?

CVE-2026-17020 is a medium-severity missing authorization vulnerability in Unknown Salon Booking System, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The Salon Booking System  WordPress plugin through 10.31.0 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-17020?


## How do I fix CVE-2026-17020?

No fix has been published for CVE-2026-17020 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-17020 being exploited?

There is no known exploitation of CVE-2026-17020 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-17020 and fix it if it is affected.

What it is: CVE-2026-17020 is a medium-severity missing authorization vulnerability in Unknown Salon Booking System, published on 10 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-17020 in the wild and no public exploit code.

Affected product: Unknown Salon Booking System. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-17020/ (Markdown: https://insights.sbomify.com/CVE-2026-17020/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-17020
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-17020
- OSV: https://osv.dev/vulnerability/CVE-2026-17020

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-17020/
Summaries are generated and may contain mistakes; the official description above is the record.