Security readout for executives and security teams
Plain-English summary
CVE-2026-1558 affects the WP Recipe Maker WordPress plugin through version 10.3.2. An unauthenticated internet user could alter specific recipe-related post metadata by referencing a post ID. The impact is integrity-focused, not full site takeover, but it can affect content trust and site data quality.
Executive priority
Treat as a near-term WordPress plugin maintenance item. Prioritize public, revenue-generating, or brand-sensitive recipe sites because attackers could tamper with content-related metadata without logging in.
Technical view
The vulnerable REST endpoint /wp-json/wp-recipe-maker/v1/integrations/instacart used a permission_callback of __return_true and lacked authorization or ownership checks for the recipeId parameter. This creates an IDOR allowing unauthenticated modification of wprm_instacart_combinations metadata for arbitrary post IDs. CVSS is 5.3, medium severity.
Likely exposure
Public WordPress sites running WP Recipe Maker up to and including 10.3.2 are potentially exposed if the vulnerable REST endpoint is reachable. Sites not using this plugin are not affected.
Exploitation context
The CVE record and Wordfence describe unauthenticated network exploitation with low complexity and no user interaction. The provided sources do not show CISA KEV listing or confirmed active exploitation in the wild.
Researcher notes
Source evidence identifies CWE-639 IDOR, the permissive REST callback, and metadata modification path. The bundle references a WordPress Trac changeset, but does not clearly name the fixed plugin release. Avoid assuming a specific patched version beyond guidance to move past 10.3.2.
Mitigation direction
- Inventory WordPress sites for WP Recipe Maker installations and versions.
- Upgrade WP Recipe Maker to a vendor-released version newer than 10.3.2 when available.
- If update unavailable, disable the plugin or Instacart integration until vendor guidance is applied.
- Restrict access to WordPress REST API endpoints where operationally feasible.
- Review post metadata for unexpected wprm_instacart_combinations changes.
Validation and detection
- Confirm whether WP Recipe Maker is installed and version is 10.3.2 or earlier.
- Review plugin changelog or WordPress Trac changeset for the authorization fix.
- Check web logs for requests to the Instacart integrations REST endpoint.
- Inspect sampled posts for unauthorized wprm_instacart_combinations metadata modifications.
- Verify remediation prevents unauthenticated metadata changes.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-639: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-1558 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Medium
- CVSS
- 5.3 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N3.91.4Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
5.3MediumVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/90a5589f-f0e9-4511-9c5e-0afcee0824d5?source=cveCVE reference
- https://plugins.trac.wordpress.org/browser/wp-recipe-maker/tags/10.3.2/includes/public/class-wprm-instacart.php#L110CVE reference
- https://plugins.trac.wordpress.org/browser/wp-recipe-maker/tags/10.3.2/includes/public/api/class-wprm-api-integrations.php#L40CVE reference
- https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3464195%40wp-recipe-maker%2Ftrunk&old=3441130%40wp-recipe-maker%2Ftrunk&sfp_email=&sfph_mail=CVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Authorization Bypass Through User-Controlled Key
Authorization Bypass Through User-Controlled Key represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.