# CVE-2026-86608: WP Recipe Maker 9.8.0 - 10.8.1 - Unauthenticated DoS via Unbounded User Meta Insertion

> Unauthenticated attackers can cause denial of service by inserting unlimited data into user metadata via an unprotected REST route.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Sep 2026
- **Updated:** 23 Sep 2026
- **Also known as:** GHSA-qqpr-953f-6p7v

## What is CVE-2026-86608?

CVE-2026-86608 is a high-severity denial of service vulnerability in Unknown WP Recipe Maker, published on 23 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The WP Recipe Maker WordPress plugin before 10.8.2 does not have any authorisation check in one of its REST routes, nor does it bound what that route stores, allowing unauthenticated users to write unlimited data into any user's metadata and to permanently prevent that account, including an administrator's, from loading.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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


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

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

## Is CVE-2026-86608 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-86608 is a high-severity denial of service vulnerability in Unknown WP Recipe Maker, published on 23 Sep 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-86608 in the wild and no public exploit code.

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

## Sources

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

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