dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-1558

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The WP Recipe Maker plugin exposes a REST API endpoint at /wp-json/wp-recipe-maker/v1/integrations/instacart that uses __return_true as its permission_callback, allowing unauthenticated access. The endpoint accepts a recipeId parameter without validating ownership or user authorization, enabling any attacker to modify wprm_instacart_combinations metadata on arbitrary posts.

MitigationUpdate WP Recipe Maker to the latest version which should implement proper permission_callback and authorization checks. Until patched, consider disabling the Instacart integration or restricting the wp-json endpoint via server configuration.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Verify WP Recipe Maker plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Recipe Maker', or check the plugin files in /wp-content/plugins/wp-recipe-maker/ for a version file
    Affected if The plugin is installed and active
  2. Determine installed plugin version
    Check the plugin header in main plugin file or WordPress plugin admin page for version number, then compare to any reported affected versions
    Affected if Version is within a range reported as vulnerable
  3. Test vulnerable REST API endpoint accessibility
    Send a GET or POST request to /wp-json/wp-recipe-maker/v1/integrations/instacart without authentication headers. Use a tool like curl: curl -s https://YOURSITE.com/wp-json/wp-recipe-maker/v1/integrations/instacart
    Affected if Endpoint returns a response without requiring authentication (status 200)
  4. Confirm Instacart integration is enabled
    Check WordPress database wp_options table for wprm_instacart_enabled option, or inspect plugin settings in WP admin under Recipe Maker > Integrations > Instacart
    Affected if Instacart integration is turned on (value is 1 or enabled)
  5. Verify endpoint permission_callback allows unauthenticated access
    Inspect plugin source code in /includes/api/ directory for the instacart endpoint registration, looking for __return_true as permission_callback
    Affected if permission_callback is set to __return_true or a function that always returns true

If the plugin is installed, the vulnerable endpoint is exposed without authentication, and the Instacart integration is enabled, then the environment is affected by CVE-2026-1558.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update WP Recipe Maker to the latest version which should implement proper permission_callback and authorization checks. Until patched, consider disabling the Instacart integration or restricting the wp-json endpoint via server configuration.

Recommended fix Moderate confidence

Version 10.3.3 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find WP Recipe Maker in the plugin list
  4. If an update is available, click 'Update Now' to update to the latest patched version
  5. Alternatively, download the latest version from wordpress.org/plugins/wp-recipe-maker and upload via Plugins > Add New > Upload Plugin
  6. After updating, verify the version number reflects the patch (version 10.3.3 or higher)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-1558 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-1558 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data