WP Recipe Maker <= 10.8.0 - Missing Authorization to Authenticated (Contributor+) Arbitrary Recipe Ownership Takeover and Unpublishing via '[wprm-recipe]' Shortcode
Strategic Overview
- Status
- Patched in 10.8.1
- Affected Plugin
- WP Recipe Maker
- Affected Version
<= 10.8.0- CVSS
- 4.3Medium
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2026-75905
At a glance
CVE-2026-75905 is a medium-severity Missing Authorization vulnerability in the WP Recipe Maker WordPress plugin, affecting versions <= 10.8.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 10.8.1; sites on affected versions should update now. Disclosed September 2026, reported by Wordfence PRISM.
Vulnerability Overview
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.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.
CWE-862: Missing Authorization
WP Recipe Maker <= 10.8.0 carries this weakness at recipe_use_author, and reaching it takes an account at Contributor level or above. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For WP Recipe Maker the fix is 10.8.1: builds <= 10.8.0 are affected, anything from 10.8.1 onward is not.
Remediation
Update to version 10.8.1, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Recipe Maker 10.8.1 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Recipe Maker
- 8.8CVE-2024-1206: WP Recipe… Authenticated (Subscriber+) SQL Injecton
CVE-2024-1206 - 6.5CVE-2024-9650: WP Recipe Maker <= 9.6.1 DOM-Based Stored XSS
CVE-2024-9650 - 6.4CVE-2025-14385: WP Recipe Maker <= 10.2.3 Stored Cross-Site Scripting
CVE-2025-14385 - 6.4CVE-2025-1503: WP Recipe Maker <= 9.8.0 Stored Cross-Site Scripting
CVE-2025-1503 - 6.4CVE-2024-0383: WP Recipe Maker <= 9.1.0 Stored Cross-Site Scripting
CVE-2024-0383 - 6.4CVE-2024-3490: WP Recipe Maker <= 9.3.1 Stored Cross-Site Scripting
CVE-2024-3490 - 6.4CVE-2024-0382: WP Recipe Maker <= 9.1.0 Stored Cross-Site Scripting
CVE-2024-0382 - 6.4CVE-2024-0255: WP Recipe Maker <= 9.1.0 Stored Cross-Site Scripting
CVE-2024-0255
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C