CVE-2025-62897

WP Recipe Maker < 10.1.0 - Unauthenticated Arbitrary Shortcode Execution

2025-09-26 00:00
Najib Sinjari

Strategic Overview

Status
Patched in 10.1.0
Affected Plugin
WP Recipe Maker
Affected Version
< 10.1.0
CVSS
5.3Medium
Weakness type
CWE-94 · Improper Control of Generation of Code ('Code Injection')
CVE
CVE-2025-62897
View all WP Recipe Maker vulnerabilities

At a glance

CVE-2025-62897 is a medium-severity Improper Control of Generation of Code ('Code Injection') vulnerability in the WP Recipe Maker WordPress plugin, affecting versions < 10.1.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 10.1.0; sites on affected versions should update now. Disclosed September 2025, reported by Najib Sinjari.

Vulnerability Overview

The The WP Recipe Maker plugin for WordPress is vulnerable to arbitrary shortcode execution in all versions up to 10.1.0 (exclusive). This is due to the software allowing users to execute an action that does not properly validate a value before running do_shortcode. This makes it possible for unauthenticated attackers to execute arbitrary shortcodes.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.

CWE-94: Improper Control of Generation of Code ('Code Injection')

Reaching this weakness in WP Recipe Maker < 10.1.0 takes no account at all. Code injection means input from a request reaches a language construct that evaluates code, so the attacker's text is executed rather than treated as data.

The injected code runs with the web server's privileges, giving the attacker the same access to the database and filesystem as WordPress itself. For WP Recipe Maker the fix is 10.1.0: builds < 10.1.0 are affected, anything from 10.1.0 onward is not.

Remediation

Update to version 10.1.0, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WP Recipe Maker 10.1.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

https://www.cve.org/CVERecord?id=CVE-2025-62897https://www.wordfence.com/threat-intel/vulnerabilities/id/0a1fa859-e06c-4ce2-9325-e0be01882a88https://nvd.nist.gov/vuln/detail/CVE-2025-62897

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C