# CVE-2026-17022: Salon Booking System – Free Version < 10.30.34 - Unauthenticated Booking Information Disclosure via Booking Wizard

> Unauthenticated attackers can access other customers' personal booking records by manipulating sequential booking identifiers in the Salon Booking System plugin.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Aug 2026
- **Updated:** 13 Aug 2026
- **Also known as:** GHSA-9jp6-8vxq-2865

## What is CVE-2026-17022?

CVE-2026-17022 is a high-severity vulnerability in Unknown Salon Booking System, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Salon Booking System  WordPress plugin before 10.30.34 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.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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


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

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

## Is CVE-2026-17022 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-17022 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17022 is a high-severity vulnerability in Unknown Salon Booking System, published on 10 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-17022 exists.

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-17022/ (Markdown: https://insights.sbomify.com/CVE-2026-17022/index.md)
```

## Sources

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

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