# CVE-2026-75905: Missing authorization in WP Recipe Maker

> Authenticated contributors can take ownership of admin recipes and unpublish them due to missing authorization checks in WP Recipe Maker.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/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:** 9 Sep 2026
- **Updated:** 9 Sep 2026
- **Also known as:** GHSA-hxrm-g829-m3g6

## What is CVE-2026-75905?

CVE-2026-75905 is a medium-severity missing authorization vulnerability in brechtvds WP Recipe Maker, published on 9 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The WP Recipe Maker plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 10.8.0. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with contributor-level access and above, to take ownership of any admin-authored recipe by rewriting its post_author to the attacker's user ID, and unpublish it by overwriting its post_status with the contributor's draft or pending post status. This requires the default 'recipe_use_author' setting to be set to 'parent' for the ownership transfer to occur, though unpublishing remains possible regardless of this setting.

Weakness: CWE-862 (Missing Authorization)

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


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

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

## Is CVE-2026-75905 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-75905 is a medium-severity missing authorization vulnerability in brechtvds WP Recipe Maker, published on 9 Sep 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-75905 in the wild and no public exploit code.

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

## Sources

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

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