# CVE-2026-110013: Salon Booking System < 10.31.9 - Unauthenticated Salon REST API Access via Predictable Access-Token

> Attackers can predict API tokens to access the booking system as an administrator, allowing unauthorized data access and modification.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** GHSA-xqfx-qcxr-5fjm

## What is CVE-2026-110013?

CVE-2026-110013 is a medium-severity vulnerability in Unknown Salon Booking System, published on 16 Oct 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.31.9 does not generate its booking-API access tokens from a secure random source, instead deriving them from a value hardcoded in the Salon Booking System  WordPress plugin before 10.31.9 and the second at which a token was issued. An attacker able to constrain when a staff or administrator token was issued can compute a valid token and access the booking API as that user, including an administrator.

Weakness: CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-110013 being exploited?

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

## Fix prompt for AI coding agents

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

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

## Sources

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

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