# CVE-2026-17021: Salon Booking System – Free Version < 10.30.34 - Unauthenticated Arbitrary Booking Total Tampering

> Unauthenticated attackers can tamper with the total cost of arbitrary bookings in the Salon Booking System WordPress plugin due to missing authorization checks.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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-jf35-5rcj-7rqm

## What is CVE-2026-17021?

CVE-2026-17021 is a medium-severity missing authorization 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 restrict access to some of its booking-modification AJAX actions and does not verify ownership of the targeted booking, allowing unauthenticated users to tamper with the stored total of arbitrary bookings.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-17021 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-17021 is a medium-severity missing authorization 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: There is no known exploitation of CVE-2026-17021 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-17021/ (Markdown: https://insights.sbomify.com/CVE-2026-17021/index.md)
```

## Sources

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

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