⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● Medium · CVSS 6.4

How to Fix CVE-2026-5357: Cross-site scripting in Download Manager

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

⚡ At a glance
Severity6.4 (Medium)
Actively exploited?No public listing in CISA KEV
Affectedcodename065 Download Manager 0 to <3.3.52
Fixed inDownload Manager 3.3.52
Type (CWE)CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

What is CVE-2026-5357?

The Download Manager plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'sid' parameter of the 'wpdm_members' shortcode in versions up to and including 3.3.52. This is due to insufficient input sanitization and output escaping on the user-supplied 'sid' shortcode attribute. The sid parameter is extracted without sanitization in the members() function and stored via update_post_meta(), then echoed directly into an HTML id attribute in the members.php template without applying esc_attr(). This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the injected page.

Am I affected?

Run the version check that matches your platform:


# Linux
dpkg -s wordpress 2>/dev/null | grep -i version
rpm -q wordpress 2>/dev/null
wordpress --version 2>/dev/null


# Windows
winget list | findstr /I "wordpress"
Get-WmiObject Win32_Product | Where-Object { $_.Name -like "*Download Manager*" } | Select-Object Name, Version

Compare what you see against the Affected row above (codename065 Download Manager 0 to <3.3.52). If your build sits inside that range, you are exposed and should patch.

How to fix CVE-2026-5357

The primary fix is to upgrade Download Manager to the patched build. Use the commands for your platform below; the patched version listed in the vendor advisory is: Download Manager 3.3.52.

Ubuntu / Debian


sudo apt-get update
sudo apt-get install --only-upgrade wordpress
wordpress --version 2>/dev/null || dpkg -s wordpress | grep -i version

RHEL / CentOS / Rocky / AlmaLinux


sudo dnf upgrade --security wordpress -y
rpm -q wordpress

SUSE / openSUSE


sudo zypper patch --category security
rpm -q wordpress

Windows (PowerShell, run as administrator)


# Check installed version
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

# Apply latest Microsoft security updates (Windows Update)
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck
Import-Module PSWindowsUpdate
Get-WindowsUpdate -MicrosoftUpdate
Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -AutoReboot

# Or via winget for application-level patches
winget upgrade --all --accept-source-agreements --accept-package-agreements

If the affected component is a third-party application, identify the package and run:


winget upgrade --id <vendor.product>

Replace <vendor.product> with the actual winget identifier (run winget search WordPress to find it).

Complete PowerShell remediation script (Windows)


# Fix script for CVE-2026-5357 affecting WordPress
# Run as administrator. Detect -> backup -> upgrade -> verify -> log.

$ErrorActionPreference = "Stop"
$LogPath  = "C:\Logs\CVE-2026-5357-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] Detecting installed version of WordPress"
    $pkg = winget list --id "WordPress" 2>$null
    Write-Host $pkg

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

    Write-Host "[3/4] Applying upgrade to Download Manager 3.3.52"
    winget upgrade --id "WordPress" --silent --accept-source-agreements --accept-package-agreements
    # Fallback: Windows Update for OS-level fixes
    if ($LASTEXITCODE -ne 0) {
        Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -ErrorAction SilentlyContinue
        Import-Module PSWindowsUpdate
        Install-WindowsUpdate -MicrosoftUpdate -AcceptAll -IgnoreReboot
    }

    Write-Host "[4/4] Verifying patched build"
    winget list --id "WordPress"
    Write-Host "Fix 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-5357 affecting WordPress
# Detect -> backup -> upgrade -> verify -> log.

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

echo "[1/4] Detecting installed version"
if command -v dpkg >/dev/null; then
    dpkg -s wordpress 2>/dev/null | grep -i version || echo "wordpress not installed via dpkg"
elif command -v rpm >/dev/null; then
    rpm -q wordpress || echo "wordpress not installed via rpm"
fi

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

echo "[3/4] Applying upgrade (target: Download Manager 3.3.52)"
if command -v apt-get >/dev/null; then
    apt-get update
    apt-get install --only-upgrade -y wordpress
elif command -v dnf >/dev/null; then
    dnf upgrade --security -y wordpress
elif command -v yum >/dev/null; then
    yum update -y wordpress
elif command -v zypper >/dev/null; then
    zypper --non-interactive patch --category security
fi

echo "[4/4] Verifying patched build"
if command -v dpkg >/dev/null; then
    dpkg -s wordpress 2>/dev/null | grep -i version
elif command -v rpm >/dev/null; then
    rpm -q wordpress
fi
echo "Done. Restart any running daemons that loaded the old library."

If you can't patch immediately

If you cannot apply the patched version today, restrict exposure with one of the following runnable controls. None replace the patch.

Network restriction (Linux, nftables)


# Block inbound traffic to the affected service from untrusted networks
sudo nft add table inet filter
sudo nft 'add chain inet filter input { type filter hook input priority 0 ; }'
sudo nft 'add rule inet filter input tcp dport {443, 80} ip saddr != 10.0.0.0/8 drop'
sudo nft list ruleset

Windows firewall isolation


# Allow only management subnet to reach the vulnerable service
New-NetFirewallRule -DisplayName "Restrict Download Manager" `
    -Direction Inbound -Action Block -RemoteAddress Any `
    -Protocol TCP -LocalPort 443
New-NetFirewallRule -DisplayName "Allow Mgmt Download Manager" `
    -Direction Inbound -Action Allow -RemoteAddress 10.0.0.0/8 `
    -Protocol TCP -LocalPort 443

Service-level fallback


# If the affected feature is optional, stop the service until the patch is applied
sudo systemctl stop wordpress
sudo systemctl disable wordpress

How to verify the fix worked


# Linux
wordpress --version 2>/dev/null || dpkg -s wordpress | grep -i version
rpm -q wordpress 2>/dev/null || true


# Windows
winget list | findstr /I "wordpress"
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Expected: the reported version is at or above Download Manager 3.3.52. Restart any services that loaded the old library (systemctl restart <service> on Linux, restart the Windows service or reboot when prompted). For network appliances, run show version on the device and confirm the build matches the patched release.

Frequently asked questions

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

Is CVE-2026-5357 actually being exploited?

According to the data sources above, no public confirmation of in-the-wild exploitation at this time. Either way, the fix is the same: apply the vendor patch.

Do I need to reboot after patching?

For OS or kernel updates, yes. For most userland packages a systemctl restart <service> is enough. Any process that loaded the old shared library keeps using it until restarted, so when in doubt, reboot.

What is the CVSS score?

6.4 (medium). Refer to the vendor advisory for the exact vector string.

Where is the official advisory?

See the References section at the bottom of this page; the vendor's URL is the authoritative source for affected builds and patched versions.

References

*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.*