Quick answers
- Is CVE-2026-89274 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-89274 being exploited in the wild.
- How severe is CVE-2026-89274?
- Critical severity, with a CVSS score of 9.1, published 19 September 2026.
- Which products and versions are affected?
- WP Recipe Maker up to and including 10.8.1.
- Is there a fix for CVE-2026-89274?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-89274 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-89274?
- Check whether you run WP Recipe Maker at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The vulnerability exists in `WPRM_Metadata::sanitize_metadata()`, which recursively calls `do_shortcode()` on recipe metadata fields including `reviewBody` (populated from approved comment content) without pre-sanitization. Unauthenticated attackers can inject shortcode tokens into comments; upon moderation approval, the shortcodes execute server-side during page rendering, and their output is exposed in JSON-LD metadata. Post-execution sanitization via `wp_strip_all_tags()` and `strip_shortcodes()` provides no protection since code execution has already occurred.
Affected products
- WP Recipe Maker WP Recipe Maker up to and including 10.8.1
Timeline
- 2026-09-19: disclosed