# CVE-2026-94230: Missing authorization in TrueBooker

> Unauthenticated attackers can create arbitrary bookings with custom prices and attach them to any customer account 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:** 19 Oct 2026
- **Updated:** 19 Oct 2026
- **Also known as:** GHSA-wv8m-75hq-ffr6

## What is CVE-2026-94230?

CVE-2026-94230 is a medium-severity missing authorization vulnerability in Unknown TrueBooker, published on 19 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The TrueBooker WordPress plugin before 1.3.0 does not have authorisation checks in some of its AJAX actions, and does not validate the submitted service price server-side, allowing unauthenticated users to create bookings at a price of their choosing and to attach them to arbitrary customer accounts.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-94230 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-94230 is a medium-severity missing authorization vulnerability in Unknown TrueBooker, published on 19 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-94230 in the wild and no public exploit code.

Affected product: Unknown TrueBooker. 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-94230/ (Markdown: https://insights.sbomify.com/CVE-2026-94230/index.md)
```

## Sources

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

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