# CVE-2026-106002: Court Reservation < 1.12.4 - Unauthenticated Arbitrary Challenge Deletion


- **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
- **Fix available:** No
- **Published:** 28 Oct 2026
- **Updated:** 28 Oct 2026
- **Also known as:** GHSA-h7f9-2hv5-88jj

## What is CVE-2026-106002?

CVE-2026-106002 is a medium-severity vulnerability in Unknown Court Reservation, published on 28 Oct 2026. 

### Official description

The Court Reservation  WordPress plugin before 1.12.4 does not perform any authorisation or nonce verification on one of its challenge-management actions, allowing unauthenticated users to delete arbitrary tournament-ladder challenge records, along with the linked court-booking event when one was scheduled.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-106002 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-106002 is a medium-severity vulnerability in Unknown Court Reservation, published on 28 Oct 2026. 
Exploitation: There is no known exploitation of CVE-2026-106002 in the wild and no public exploit code.

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

## Sources

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

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