CVE-2026-15099 WP Delicious <= 1.10.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via 'steps' Block Attribute

Q: What is CVE-2026-15099?

CVE-2026-15099 is a medium-severity cross-site scripting vulnerability in wpdelicious WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes), published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Q: Is CVE-2026-15099 being exploited?

There is no known exploitation of CVE-2026-15099 in the wild and no public exploit code.

Q: How do I fix CVE-2026-15099?

No fix has been published for CVE-2026-15099 yet. Limit exposure of the affected software until one is available.

Medium 6.4 Published 16 Jul 2026 Updated 16 Jul 2026

Authenticated attackers can inject malicious scripts via recipe steps, leading to code execution or account takeover when victims interact with the content.

Exploited in the wild: Not known
Login needed: Any signed-in user
Attackable: Over the internet
Victim action needed: Not needed
Fix: None listed

What is CVE-2026-15099?

CVE-2026-15099 is a medium-severity cross-site scripting vulnerability in wpdelicious WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes), published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

Official description

The Delicious Recipes plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'steps' block attribute in versions up to, and including, 1.10.2. This is due to insufficient input sanitization and output escaping in the wrap_direction_text() function, which interpolates the user-supplied href value from nested link nodes ($node['props']['href']) directly into an anchor tag via sprintf() at line 1627 without esc_url() or any URL scheme validation. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts (including javascript: URIs) in pages that will execute whenever a user (such as an editor or administrator previewing the pending post) accesses an injected page and clicks the malicious link.

Weakness: CWE-79

Which versions are affected by CVE-2026-15099?

How do I fix CVE-2026-15099?

No fix has been published for CVE-2026-15099 yet. Limit exposure of the affected software until one is available.

Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.

Is CVE-2026-15099 being exploited?