Recipe Maker 9.8.0 - 10.8.1 - Unauthenticated Arbitrary User Meta Corruption
Strategic Overview
- Status
- Patched in 10.8.2
- Affected Plugin
- WP Recipe Maker
- Affected Version
9.8.0 – 10.8.1- CVSS
- 5.3Medium
- Weakness type
- CWE-400 · Uncontrolled Resource Consumption
- CVE
CVE-2026-86608
At a glance
CVE-2026-86608 is a medium-severity Uncontrolled Resource Consumption vulnerability in the WP Recipe Maker WordPress plugin, affecting versions 9.8.0 – 10.8.1. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 10.8.2; sites on affected versions should update now. Disclosed September 2026, reported by Isuka sanuj.
Vulnerability Overview
The Recipe Maker plugin for WordPress is vulnerable to Denial of Service in versions 9.8.0 through 10.8.1. This is due to a missing authentication check on the /notice REST route and no validation or bound on the notice ID or target user ID passed to add_user_meta. This makes it possible for unauthenticated attackers to write unlimited arbitrary rows into any user's metadata via the unauthenticated REST notice-dismissal endpoint, permanently preventing affected accounts from loading.
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 privileges on the target site, and no interaction from a victim user.
CWE-400: Uncontrolled Resource Consumption
Reaching this weakness in WP Recipe Maker 9.8.0 – 10.8.1 takes no account at all. Uncontrolled resource consumption means a request can make the server do an amount of work it never bounds, because the size or repetition of the job is taken from the request rather than capped by the code.
A single caller can hold PHP workers, database connections or disk open long enough to slow the site for everyone, without needing any account or any other flaw. For WP Recipe Maker the fix is 10.8.2: builds 9.8.0 – 10.8.1 are affected, anything from 10.8.2 onward is not.
Remediation
Update to version 10.8.2, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Recipe Maker 10.8.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in WP Recipe Maker
- 9.1CVE-2026-89274: WP Recipe Maker Arbitrary Shortcode Execution
CVE-2026-89274 - 8.8CVE-2024-1206: WP Recipe… Authenticated (Subscriber+) SQL Injecton
CVE-2024-1206 - 6.5CVE-2026-86601: Recipe Maker <= 10.8.1 Arbitrary Shortcode Execution
CVE-2026-86601 - 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C