Code Injection in WP Recipe Maker (WordPress plugin) (CVE-2026-89274)
Summary
Code injection in WP Recipe Maker (WordPress plugin) (CVE-2026-89274). Confidential information can be exposed externally. Exploitable via reviewBody.
Original description
The description as published by the source.
The WP Recipe Maker plugin for WordPress is vulnerable to Arbitrary Shortcode Execution in all versions up to, and including, 10.8.1. The vulnerability exists because WPRM_Metadata::sanitize_metadata() recursively calls do_shortcode() on every scalar field of the recipe's structured metadata array — including the reviewBody field, which is populated verbatim from the comment_content of approved wprm-comment-rating comments — without sanitizing or stripping shortcode tokens before execution; the subsequent wp_strip_all_tags() and strip_shortcodes() calls operate only on the output string after execution has already fully occurred, providing no protection against server-side shortcode invocation. This makes it possible for unauthenticated attackers to execute arbitrary registered WordPress shortcodes server-side on every recipe page render, causing shortcode output — such as attachment captions, private post fields, or other data exposed by installed shortcodes — to be embedded in the page's JSON-LD reviewBody metadata and disclosed to all visitors who load the recipe page. Successful exploitation requires the attacker's rated comment to pass the site's comment approval threshold, either via auto-approval or moderator action, before the injected shortcode begins executing on page loads.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-89274 has been found in WP Recipe Maker (WordPress plugin).
Attackers can target a specific entry point like reviewBody over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 9.1/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "WP Recipe Maker (WordPress plugin) CVE-2026-89274" on the vendor's site.
CVE-2026-89274 (WP Recipe Maker (WordPress plugin)) — CWE-94 / CVSS v3 9.1
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: reviewBody / comment_content
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
Arbitrary code execution (CWE-94) exists in WP Recipe Maker (WordPress plugin). Attackers reach the vulnerable code path via reviewBody without authentication.
Check the vendor advisory for the affected versions of WP Recipe Maker (WordPress plugin). Attack surface: reviewBody / comment_content.
Severity: Critical (CVSS 9.1/10). Confidential information can be exposed externally.
Update to the patched release per vendor advisory.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
Audit SBOM/dependencies for affected components.資産台帳・SBOM・依存マニフェストで WP Recipe Maker (WordPress plugin) を使っているサービスとバージョンを洗い出す。
-
2Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。