Recipe Maker <= 10.9.1 - Unauthenticated Information Exposure
Strategic Overview
- Status
- Patched in 10.9.2
- Affected Plugin
- WP Recipe Maker
- Affected Version
<= 10.9.1- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2026-122060
At a glance
CVE-2026-122060 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WP Recipe Maker WordPress plugin, affecting versions <= 10.9.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.9.2; sites on affected versions should update now. Disclosed November 2026, reported by wellknown.info.
Vulnerability Overview
The Recipe Maker plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 10.9.1. This makes it possible for unauthenticated attackers to extract sensitive user or configuration data.
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-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in WP Recipe Maker <= 10.9.1 takes no account at all. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For WP Recipe Maker the fix is 10.9.2: builds <= 10.9.1 are affected, anything from 10.9.2 onward is not.
Remediation
Update to version 10.9.2, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP Recipe Maker 10.9.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Same weakness class
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-2026-119489: WP Recipe Maker <= 10.9.1 Stored Cross-Site Scripting
CVE-2026-119489 - 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
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C