CVE-2025-14742

WP Recipe Maker <= 10.6.0 - Missing Authorization to Authenticated (Subscriber+) Sensitive Information Exposure

2026-02-24 21:09
Abhinav Jaswal (wrath_exe)

Strategic Overview

Status
Patched in 10.6.1
Affected Plugin
WP Recipe Maker
Affected Version
<= 10.6.0
CVSS
4.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2025-14742
View all WP Recipe Maker vulnerabilities

At a glance

CVE-2025-14742 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP Recipe Maker WordPress plugin, affecting versions <= 10.6.0. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 10.6.1; sites on affected versions should update now. Disclosed February 2026, reported by Abhinav Jaswal (wrath_exe).

Vulnerability Overview

The WP Recipe Maker plugin for WordPress is vulnerable to unauthorized access of data due to a missing capability check on the 'ajax_search_recipes' and 'ajax_get_recipe' functions in all versions up to, and including, 10.6.0 This makes it possible for authenticated attackers, with Subscriber-level access and above, to retrieve sensitive recipe information including draft, pending, and private recipes that they shouldn't be able to access.

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 interaction from a victim user.

CWE-639: Authorization Bypass Through User-Controlled Key

WP Recipe Maker <= 10.6.0 carries this weakness at ajax_search_recipes, and reaching it takes an account at Subscriber level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.

Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For WP Recipe Maker the fix is 10.6.1: builds <= 10.6.0 are affected, anything from 10.6.1 onward is not.

Remediation

Update to version 10.6.1, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: WP Recipe Maker 10.6.1 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2025-14742https://www.wordfence.com/threat-intel/vulnerabilities/id/10c17e74-dced-483e-bcaf-00ff5b11059chttps://nvd.nist.gov/vuln/detail/CVE-2025-14742

Related records

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