Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-89274 – Unauthenticated Arbitrary Shortcode Execution – WP Recipe Maker ≤ 10.8.1

Be the first to know when new zero-days emerge:

Summary

CVE-2026-89274 is a critical arbitrary shortcode execution vulnerability in the WP Recipe Maker plugin for WordPress, affecting all versions up to and including 10.8.1. The flaw allows unauthenticated attackers to trigger server-side execution of any registered WordPress shortcode by submitting a specially crafted recipe rating comment, exposing sensitive data embedded in the resulting page output. The issue carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: The plugin’s WPRM_Metadata::sanitize_metadata() function recursively calls do_shortcode() on every scalar field of a recipe’s structured metadata array — including the reviewBody field, which is populated verbatim from the comment_content of approved wprm-comment-rating comments — before any sanitization is applied.
  • Ineffective sanitization order: The subsequent wp_strip_all_tags() and strip_shortcodes() calls operate only on the already-rendered output string, i.e., after shortcode execution has completed. This provides no actual protection against the injected code running.
  • Trigger conditions: An attacker submits a recipe rating/comment containing a malicious shortcode payload. Once the comment is approved — whether via the site’s auto-approval settings or manual moderator action — the plugin executes the embedded shortcode server-side on every subsequent render of the recipe page.
  • Attack vector: Network-based, unauthenticated (AV:N/PR:N/UI:N). No prior authentication or user interaction is required beyond normal comment submission and approval.
  • Impact: Successful exploitation allows execution of any shortcode registered on the site (including those exposing attachment captions, private post fields, or other sensitive data via installed plugins/themes). The output of the invoked shortcode can be embedded into the page’s JSON-LD reviewBody metadata and disclosed to every visitor who loads the affected recipe page, resulting in high-impact information disclosure and integrity loss with no direct availability impact.

Affected software

  • WP Recipe Maker (WordPress plugin) by brechtvds — all versions up to and including 10.8.1

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
  • CWE-94: Improper Control of Generation of Code (‘Code Injection’)

Mitigation and recommended actions

  • Immediate: Upgrade WP Recipe Maker to version 10.8.2 or later, which fixes shortcode execution of comment text in recipe metadata.
  • If immediate patching is not possible:
    • Disable automatic approval of recipe rating comments and enable strict manual moderation to prevent malicious comments from reaching the approved state.
    • Consider temporarily disabling the recipe comment/rating feature until the plugin is updated.
    • Review recently approved recipe comments for shortcode-like syntax (e.g., strings enclosed in square brackets) and remove any suspicious entries.
    • Restrict or audit which shortcodes are registered/available on the site, since any registered shortcode could be leveraged for data exposure.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge