mediumCVE-2026-15099

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

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.

ProductWP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes)
Risk levelMedium
EPSSNot scored yet
UpdatedJuly 16, 2026

Quick answer

WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes) should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.

Who is affected

Affected versions

  • *-1.10.2

Fixed versions

  • 1.10.3

How to fix it

CVE-2026-15099 is a cross-site scripting issue in WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes). Update from *-1.10.2 to 1.10.3 or newer. Keep the fix simple: upgrade first, then test the normal user flow.

  1. Find every place where WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes) is installed or used.
  2. Upgrade WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes) to 1.10.3 or a newer fixed release from the vendor.
  3. If you cannot upgrade right away, limit access to the affected feature until the update is done.
  4. Restart or redeploy the service if the product needs it after the update.

Scan now. Google sign-in is only needed to unlock fix guidance.

Verify the fix

  • Confirm the installed version is 1.10.3 or newer.
  • Run a normal login, admin, and user flow to make sure the site still works.
  • Check logs for new errors after the update.

Related categories

Trusted references

FAQ

What is affected by CVE-2026-15099?

WP Delicious – Recipe Plugin for Food Bloggers (formerly Delicious Recipes) versions listed as affected should be reviewed: *-1.10.2.

What should I fix first?

Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.

How do I confirm the fix worked?

Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.

How are Fixnx security risk categories chosen?

Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.