# Recipe Maker <= 10.9.1 - Authenticated (Contributor+) Stored Cross-Site Scripting via Custom Fields

- **ID:** WPSEC-2026-2229
- **Plugin:** WP Recipe Maker (`wp-recipe-maker`), https://wordpress.org/plugins/wp-recipe-maker/
- **Affected versions:** all versions before 10.9.2
- **Fixed in:** 10.9.2 (Update to 10.9.2 or later.)
- **Severity:** Medium 6.4 (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N)
- **Weakness:** CWE-79
- **Usage among sites WPSec scans:** plugin Medium, affected versions Medium (as of 2026-11-03)
- **Attack surface analysis:** https://attacksurface.wpsec.com/plugin/wp-recipe-maker
- **Fix released:** 2026-10-30
- **Published:** 2026-11-03
- **URL:** https://wpsec.com/vuln/WPSEC-2026-2229/

## Description

The WP Recipe Maker plugin for WordPress is vulnerable to Stored Cross-Site Scripting via WordPress's generic Custom Fields feature in all versions up to, and including, 10.9.1. The plugin's wprm_ and wprmp_ post meta keys are not marked as protected, so raw values can be written to recipe and list fields without going through the plugin's sanitization. Some of these fields, such as recipe notes, are output without escaping. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts into recipes and lists they can edit that will execute whenever a user accesses a page displaying them.

## References

- https://wpsec.com/vuln/WPSEC-2026-2229/
- https://plugins.svn.wordpress.org/wp-recipe-maker/tags/10.9.2/
- https://wordpress.org/plugins/wp-recipe-maker/

Source: WPSec, https://wpsec.com/vuln/WPSEC-2026-2229/

License: CC BY 4.0 (https://creativecommons.org/licenses/by/4.0/). Free to use, share and adapt, also commercially, if you credit WPSec and link to this advisory.
