# CVE-2026-110012: Salon Booking System < 10.31.3 - Subscriber+ Booking PII Disclosure via REST bookings/upcoming

> Authenticated subscribers can access all customer booking records and personal data via unrestricted REST API routes in the Salon Booking System plugin.

- **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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-jqvh-5w26-v59x

## What is CVE-2026-110012?

CVE-2026-110012 is a medium-severity missing authorization vulnerability in Unknown Salon Booking System, published on 16 Oct 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 before 10.31.3 does not restrict several of its booking REST API routes to users with the appropriate capability, allowing any authenticated user such as a subscriber to read every customer's booking records, including their personal data.

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

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


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

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

## Is CVE-2026-110012 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-110012 is a medium-severity missing authorization vulnerability in Unknown Salon Booking System, published on 16 Oct 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-110012 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-110012/ (Markdown: https://insights.sbomify.com/CVE-2026-110012/index.md)
```

## Sources

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

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