# Cooked <= 1.16.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Recipe Fields

- **ID:** WPSEC-2026-2269
- **Plugin:** Cooked – Recipe Management (`cooked`), https://wordpress.org/plugins/cooked/
- **Affected versions:** all versions before 1.17.0
- **Fixed in:** 1.17.0 (Update to 1.17.0 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 Low, affected versions Low (as of 2026-11-03)
- **Attack surface analysis:** https://attacksurface.wpsec.com/plugin/cooked
- **Fix released:** 2026-11-01
- **Published:** 2026-11-03
- **URL:** https://wpsec.com/vuln/WPSEC-2026-2269/

## Description

The Cooked plugin for WordPress is vulnerable to Stored Cross-Site Scripting via recipe fields such as the excerpt, notes, and directions in all versions up to, and including, 1.16.2. This is due to the [cooked-info] shortcode registering a wp_kses_allowed_html filter that permits <script> tags and never removing it, so later wp_kses_post calls on the same request allow scripts. Recipe input was also entity-decoded only once before sanitization and decoded again at output, which let double-encoded markup survive. This makes it possible for authenticated attackers with contributor-level access and above to inject arbitrary web scripts in pages that execute whenever a user accesses an injected page.

## References

- https://wpsec.com/vuln/WPSEC-2026-2269/
- https://plugins.svn.wordpress.org/cooked/tags/1.17.0/
- https://wordpress.org/plugins/cooked/

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

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.