● Medium · CVSS 5.3

How to Fix CVE-2026-1558: Cwe-639 authorization bypass through user-controlled key in WP Recipe Maker

Q: What is the CVSS score for CVE-2026-1558?

5.3 (Medium). Vector: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`.

Q: Where is the official advisory for CVE-2026-1558?

The vendor advisory is at [https://www.wordfence.com/threat-intel/vulnerabilities/id/90a5589f-f0e9-4511-9c5e-0afcee0824d5?source=cve](https://www.wordfence.com/threat-intel/vulnerabilities/id/90a5589f-f0e9-4511-9c5e-0afcee0824d5?source=cve). The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-1558.

By Sai Kiran Pandrala. Last verified: 2026-05-25.

CVE-2026-1558 is a cwe-639 authorization bypass through user-controlled key in brechtvds WP Recipe Maker. The fix is to apply the vendor patch noted below.

⚡ At a glance


Severity	5.3 (Medium)
Actively exploited?	No public listing in CISA KEV
Affected	WP Recipe Maker 0 to <=10.3.2
Fixed in	See vendor advisory
Type (CWE)	CWE-639 Authorization Bypass Through User-Controlled Key

What is CVE-2026-1558?

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. The CVSS base score is 5.3 (Medium). The official advisory is at https://www.wordfence.com/threat-intel/vulnerabilities/id/90a5589f-f0e9-4511-9c5e-0afcee0824d5?source=cve.

Am I affected?

Check the version of WP Recipe Maker you are running and compare it against the Affected row above (WP Recipe Maker 0 to <=10.3.2). If your build sits inside the affected range, you must patch.

Run the version check that fits your platform:


# Linux package check
dpkg -s wp-recipe-maker 2>/dev/null | grep -i ^Version
rpm -q wp-recipe-maker 2>/dev/null
command -v wp-recipe-maker >/dev/null && wp-recipe-maker --version 2>/dev/null


# Windows (PowerShell)
Get-Package -Name "*WP Recipe Maker*" -ErrorAction SilentlyContinue | Select-Object Name, Version
winget list --name "WP Recipe Maker" 2>$null

How to fix CVE-2026-1558

Upgrade WP Recipe Maker to a patched build: See vendor advisory. The vendor advisory is the source of truth for the exact fixed version.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade wp-recipe-maker
dpkg -s wp-recipe-maker | grep -i ^Version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --refresh wp-recipe-maker -y
# or for older releases:
sudo yum update wp-recipe-maker -y
rpm -q wp-recipe-maker

SUSE / openSUSE


sudo zypper refresh
sudo zypper update wp-recipe-maker
rpm -q wp-recipe-maker

Node.js / npm


# Update the affected package in your project
npm install WP Recipe Maker@latest
npm ls WP Recipe Maker
npm audit fix

PHP / Composer


composer update brechtvds/wp-recipe-maker 2>/dev/null || composer update
composer show | head -20

WordPress


# Update via WP-CLI
wp plugin update --all
wp core update

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-1558 affecting WP Recipe Maker
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-1558-fix-$(Get-Date -Format yyyyMMdd-HHmmss).log"
New-Item -ItemType Directory -Force (Split-Path $LogPath) | Out-Null
Start-Transcript -Path $LogPath -Append

try {
    Write-Host "[1/4] Detect installed version"
    $pkg = Get-Package -Name "*WP Recipe Maker*" -ErrorAction SilentlyContinue
    if ($pkg) { $pkg | Format-Table Name, Version }
    else { Write-Host "Not detected via Get-Package; try winget list" }

    Write-Host "[2/4] Backup configuration"
    $backup = "C:\Backup\wp-recipe-maker-$(Get-Date -Format yyyyMMdd)"
    New-Item -ItemType Directory -Force $backup | Out-Null
    Get-ChildItem "C:\ProgramData\WP Recipe Maker" -ErrorAction SilentlyContinue |
        Copy-Item -Destination $backup -Recurse -Force -ErrorAction SilentlyContinue

    Write-Host "[3/4] Apply the upgrade to See vendor advisory"
    winget upgrade --name "WP Recipe Maker" --silent --accept-source-agreements --accept-package-agreements
    if ($LASTEXITCODE -ne 0) {
        # Fallback: pull latest via OS update channel
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verify the patched build"
    winget list --name "WP Recipe Maker"
    Write-Host "Patch applied. Reboot if prompted."
    exit 0
} catch {
    Write-Error "Patch failed: $_"
    exit 1
} finally {
    Stop-Transcript
}

Complete Bash remediation script (Linux)


#!/usr/bin/env bash
# Fix script for CVE-2026-1558 affecting WP Recipe Maker
# Detect -> backup -> upgrade -> verify -> log.

set -euo pipefail
LOG="/var/log/cve-2026-1558-fix-$(date +%Y%m%d-%H%M%S).log"
exec > >(tee -a "$LOG") 2>&1

echo "[1/4] Detect installed version"
if command -v dpkg >/dev/null; then
    dpkg -s wp-recipe-maker 2>/dev/null | grep -i ^Version || echo "wp-recipe-maker not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q wp-recipe-maker || echo "wp-recipe-maker not installed via rpm"
fi

echo "[2/4] Backup configuration"
BACKUP="/root/backup-cve-2026-1558-$(date +%Y%m%d)"
mkdir -p "$BACKUP"
for d in /etc/wp-recipe-maker /etc/wp-recipe-maker.d /etc/wp-recipe-maker.conf; do
    [ -e "$d" ] && cp -a "$d" "$BACKUP/" || true
done

echo "[3/4] Apply the upgrade (target: See vendor advisory)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y wp-recipe-maker
elif command -v dnf >/dev/null; then
    dnf upgrade --refresh -y wp-recipe-maker
elif command -v yum >/dev/null; then
    yum update -y wp-recipe-maker
elif command -v zypper >/dev/null; then
    zypper --non-interactive update wp-recipe-maker
fi

echo "[4/4] Verify the patched build"
if command -v dpkg >/dev/null; then
    dpkg -s wp-recipe-maker 2>/dev/null | grep -i ^Version
elif command -v rpm >/dev/null; then
    rpm -q wp-recipe-maker
fi
echo "Done. Restart any service that loaded the old library."

If you can't patch immediately

Apply at least one of the following inline controls until you can deploy the patched build. None replace the upgrade.

Restrict exposure with nftables (Linux)


# Allow only trusted CIDR to reach the affected service ports
sudo nft add table inet filter 2>/dev/null || true
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }' 2>/dev/null || true
sudo nft 'add rule inet filter input tcp dport {80, 443} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Block at the host firewall (Windows)


New-NetFirewallRule -DisplayName "Block-CVE-2026-1558" -Direction Inbound -Action Block -Protocol TCP -LocalPort 80,443 -RemoteAddress Any -Enabled True
Get-NetFirewallRule -DisplayName "Block-CVE-2026-1558"

Disable the affected service (Linux)


sudo systemctl stop wp-recipe-maker 2>/dev/null || true
sudo systemctl disable wp-recipe-maker 2>/dev/null || true

If the vendor advisory lists an official workaround, prefer that wording verbatim. If no workaround is published, the only safe remediation is the patch.

How to verify the fix worked

After upgrading, confirm the installed version matches the patched build and that no old library is still loaded by a long-running process.


# Linux
dpkg -s wp-recipe-maker 2>/dev/null | grep -i ^Version
rpm -q wp-recipe-maker 2>/dev/null || true
# Pid map check for old library handles
sudo lsof +c0 2>/dev/null | grep -i "DEL.*lib" || true


# Windows
Get-Package -Name "*WP Recipe Maker*" | Select-Object Name, Version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above See vendor advisory. Restart the affected service (systemctl restart <service> on Linux, or restart the Windows service) so it loads the patched binary.

Frequently asked questions

Other vulnerabilities in the same area that are worth patching alongside this one:

How to Fix CVE-2026-33285: Input Validation Flaw in liquidjs — Input Validation Flaw in liquidjs
How to Fix CVE-2026-25231: Access Control Bypass in FileRise — Access Control Bypass in FileRise
How to Fix CVE-2026-29044: Access Control Bypass in everest-core , Access Control Bypass in everest-core
How to Fix CVE-2026-40323: Insufficient verification of data in sp1 , Insufficient verification of data in sp1
How to Fix CVE-2026-33477: Access Control Bypass in FileRise , Access Control Bypass in FileRise

Is CVE-2026-1558 actively exploited?

There is no public confirmation of exploitation in the wild listed in CISA KEV at the time of this writing. Patch anyway. Public exploits commonly follow disclosure within weeks.

Do I need to reboot after patching CVE-2026-1558?

For kernel and OS-level updates, yes. For most userland packages a systemctl restart <service> is enough on Linux, and restarting the Windows service or app on Windows. Any process that loaded the old library keeps using it until restarted.

What is the CVSS score for CVE-2026-1558?

5.3 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N.

Where is the official advisory for CVE-2026-1558?

The vendor advisory is at https://www.wordfence.com/threat-intel/vulnerabilities/id/90a5589f-f0e9-4511-9c5e-0afcee0824d5?source=cve. The NVD record is at https://nvd.nist.gov/vuln/detail/CVE-2026-1558.

References

Official vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/90a5589f-f0e9-4511-9c5e-0afcee0824d5?source=cve
NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-1558
CISA KEV catalog: https://www.cisa.gov/known-exploited-vulnerabilities-catalog
Additional reference: https://plugins.trac.wordpress.org/browser/wp-recipe-maker/tags/10.3.2/includes/public/class-wprm-instacart.php#L110
Additional reference: https://plugins.trac.wordpress.org/browser/wp-recipe-maker/tags/10.3.2/includes/public/api/class-wprm-api-integrations.php#L40
Additional 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=

*Written by Sai Kiran Pandrala. Assembled from the official vendor advisory, NVD record, and CISA KEV listing on 2026-05-25. Always confirm against the vendor's advisory before applying changes in production.*