CVE-2026-1558

WP Recipe Maker <= 10.3.2 - Insecure Direct Object Reference to Unauthenticated Arbitrary Post Metadata Modification via 'recipeId' Parameter

2026-02-26 15:59
Quốc Huy (jtwings)

Strategic Overview

Status
Patched in 10.3.3
Affected Plugin
WP Recipe Maker
Affected Version
<= 10.3.2
CVSS
5.3Medium
Weakness type
CWE-639 · Authorization Bypass Through User-Controlled Key
CVE
CVE-2026-1558
View all WP Recipe Maker vulnerabilities

At a glance

CVE-2026-1558 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the WP Recipe Maker WordPress plugin, affecting versions <= 10.3.2. 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.3.3; sites on affected versions should update now. Disclosed February 2026, reported by Quốc Huy (jtwings).

Vulnerability Overview

The WP Recipe Maker plugin for WordPress is vulnerable to an Insecure Direct Object Reference (IDOR) in versions up to, and including, 10.3.2. This is due to the /wp-json/wp-recipe-maker/v1/integrations/instacart REST API endpoint's permission_callback being set to __return_true and a lack of subsequent authorization or ownership checks on the user-supplied recipeId. This makes it possible for unauthenticated attackers to overwrite arbitrary post metadata (wprm_instacart_combinations) for any post ID on the site via the recipeId parameter.

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-639: Authorization Bypass Through User-Controlled Key

Reaching this weakness in WP Recipe Maker <= 10.3.2 takes no account at all. 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.3.3: builds <= 10.3.2 are affected, anything from 10.3.3 onward is not.

Remediation

Update to version 10.3.3, or a newer patched version

How does WordSec protect against this?

This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: WP Recipe Maker 10.3.3 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-1558https://www.wordfence.com/threat-intel/vulnerabilities/id/90a5589f-f0e9-4511-9c5e-0afcee0824d5https://nvd.nist.gov/vuln/detail/CVE-2026-1558

Related records

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