CVE-2026-120557: WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes) · Cross-site Scripting
Affects WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes)Source CVE Database V5
Not known to be exploited · CVSS 6.4 Medium.
Data as of 18 Nov 2026, 09:54 UTC
Thin evidence
One scorer or none| CNA (Wordfence) | CVSS 3.1 | 6.4 |
|---|
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:NExploitation evidence
Disclosed: evidence found.
CVE published 18 Nov 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| wpdeliciousWP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes) | Affected
| Fixed in– |
AI-suggested
Users should restrict contributor-level access carefully and consider disabling or removing the affected plugin until a fix is released. Monitor vendor advisories for updates. Applying strict input validation or output escaping at the application level may reduce risk but is not a complete solution.
Description
The WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes) for WordPress contains a stored cross-site scripting (XSS) vulnerability in the 'details[].icon' parameter. This affects all versions up to and including 1.10.11. Authenticated users with contributor-level access or higher can inject malicious scripts that execute when other users view the affected pages. The vulnerability arises due to insufficient input sanitization and output escaping, and it bypasses standard WordPress content filters because of how Gutenberg serializes block attributes.
References
- wordfence.com/threat-intel/vulnerabilities/id/6b15c08c-5ad2-42e0-8301-b13195944838?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/delicious-recipes/tags/1.10.10/src/blocks/dynamic-blocks/class-delicious-dynamic-recipe-card.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/delicious-recipes/tags/1.10.10/src/blocks/dynamic-blocks/class-delicious-dynamic-recipe-card.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/delicious-recipes?rev=3804205 (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3804205/delicious-recipes/trunk/src/blocks/dynamic-blocks/class-delicious-dynamic-recipe-card.php (opens in a new tab)