● High · CVSS 8.1

How to Fix CVE-2026-5436: MW WP Form <= 5.1.1 - Unauthenticated Arbitrary File Move via regenerate_upload_file_keys

Q: Is CVE-2026-5436 being actively exploited?

Not at the time of writing. It is not listed in CISA's Known Exploited Vulnerabilities catalog. That status can change, so monitor the vendor advisory and the KEV catalog if the system is exposed.

Q: How severe is CVE-2026-5436?

CVSS rates it 8.1 (High). Use that score to set your patch priority alongside the other items in your queue.

Q: Do I have to take MW WP Form offline to apply the patch?

It depends on the deployment. High-availability or clustered installs can usually patch one node at a time with no full outage. Standalone installs typically need a short restart. Always follow the vendor's documented upgrade steps.

Q: What if my vulnerability scanner still flags CVE-2026-5436 after I patch?

Re-run the scan after a service restart, then confirm the scanner's plugin set is up to date. Some scanners detect by banner version only and lag the official fix metadata by a release.

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

How to Fix CVE-2026-28717: Cwe-276 in Acronis Cyber Protect 17 — Cwe-276 in Acronis Cyber Protect 17
How to Fix CVE-2026-29111: Critical Vulnerability in systemd — Critical Vulnerability in systemd
How to Fix CVE-2026-4325: Red Hat build of Keycloak 26.2 (Bundle Sibling) , Red Hat build of Keycloak 26.2 (Bundle Sibling)
How to Fix CVE-2026-40189: Missing authorization in goshs , Missing authorization in goshs
How to Fix CVE-2026-3962: Cross Site Scripting in Machine-Learning-Web-Apps , Cross Site Scripting in Machine-Learning-Web-Apps

*By Sai Kiran Pandrala*

Last verified: 2026-05-25

⚡ At a glance


Severity	CVSS 8.1, High
Actively exploited?	No
Affected	Inc2734 MW WP Form (0 <= 5.1.1)
Fixed in	See vendor advisory
Type (CWE)	CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

CVE-2026-5436 is a mw wp form <= 5.1.1 - unauthenticated arbitrary file move via regenerate_upload_file_keys in Inc2734 MW WP Form. The fix is to upgrade to see vendor advisory and apply the runnable commands below.

What is CVE-2026-5436?

The MW WP Form plugin for WordPress is vulnerable to Arbitrary File Move/Read in all versions up to and including 5.1.1. This is due to insufficient validation of the $name parameter (upload field key) passed to the generate_user_file_dirpath() function, which uses WordPress's path_join() , a function that returns absolute paths unchanged, discarding the intended base directory. The attacker-controlled key is injected via the mwf_upload_files[] POST parameter, which is loaded into the plugin's Data model via _set_request_valiables().

In practical terms, a successful attacker gets remote code execution on the affected system. There is no confirmed in-the-wild exploitation listed in CISA's KEV catalog at the time of writing, but the CVSS rating still warrants prompt patching.

Am I affected?

You are affected if you run Inc2734 MW WP Form at a version listed in the Affected row above. Probe your installed build with the commands below.


# Confirm the installed version via your package manager
dpkg -l | grep -i mw   # Debian/Ubuntu
rpm -qa | grep -i mw   # RHEL/CentOS/Rocky

How to fix CVE-2026-5436

The primary fix is to upgrade to the patched build listed in the Fixed in row above (See vendor advisory). Pick the platform that matches your install and run the commands below.

Linux (Ubuntu / Debian)


# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/bc308993-7fc5-41db-a396-f05e95fe47b8?source=cve
sudo apt-get update
sudo apt-get install --only-upgrade mw-wp-form
# Confirm the installed version meets or exceeds <patched-version>
dpkg -s mw-wp-form | grep ^Version

Linux (RHEL / CentOS / Rocky)


sudo dnf upgrade --security mw-wp-form -y
rpm -q mw-wp-form

Windows (PowerShell, admin)


# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/bc308993-7fc5-41db-a396-f05e95fe47b8?source=cve
winget upgrade --id 'Inc2734.MWWPForm' --silent --accept-source-agreements --accept-package-agreements
# If winget doesn't know the product, download the patched installer from the vendor and:
Start-Process -FilePath "$env:TEMP\MWWPForm-<patched-version>.msi" -ArgumentList '/qn /norestart' -Wait

PowerShell script (Windows): detect, back up, upgrade, verify, log


# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/bc308993-7fc5-41db-a396-f05e95fe47b8?source=cve
# Run as Administrator
$ErrorActionPreference = 'Stop'
$log = "$env:ProgramData\MWWPForm-Patch-CVE-2026-5436.log"
function Write-Log($msg) { "$(Get-Date -Format s)  $msg" | Tee-Object -FilePath $log -Append }

Write-Log "Starting CVE-2026-5436 remediation for Inc2734 MW WP Form"

# 1. Detect: replace the path/version probe with one valid for your install
$installed = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*MW*' } |
    Select-Object -First 1 -ExpandProperty Version)
Write-Log "Detected version: $installed"

if (-not $installed) {
    Write-Log "Product not installed on this host; nothing to do."
    return
}
if ([version]$installed -ge [version]'<patched-version>') {
    Write-Log "Already at fixed version $installed; no action needed."
    return
}

# 2. Backup configuration to a timestamped folder
$backup = "$env:ProgramData\MWWPForm-Backup-$(Get-Date -Format yyyyMMdd-HHmm)"
New-Item -ItemType Directory -Path $backup -Force | Out-Null
$src = "$env:ProgramFiles\Inc2734\MW WP Form"
if (Test-Path $src) { Copy-Item -Path $src -Destination $backup -Recurse -Force }
Write-Log "Backed up config to $backup"

# 3. Apply the patched installer
$installer = "$env:TEMP\MWWPForm-<patched-version>.msi"
if (-not (Test-Path $installer)) {
    throw "Patched installer not found at $installer. Stage it from your software repo first."
}
Start-Process msiexec.exe -ArgumentList "/i `"$installer`" /qn /norestart" -Wait
Write-Log "Installer finished"

# 4. Verify
$verify = (Get-WmiObject -Class Win32_Product |
    Where-Object { $_.Name -like '*MW*' } |
    Select-Object -First 1 -ExpandProperty Version)
if ([version]$verify -ge [version]'<patched-version>') {
    Write-Log "SUCCESS: now at $verify (>= <patched-version>)"
} else {
    Write-Log "FAILURE: still at $verify after install"
    exit 1
}

Bash script (Linux): detect, back up, upgrade, verify, log


# Vendor advisory: https://www.wordfence.com/threat-intel/vulnerabilities/id/bc308993-7fc5-41db-a396-f05e95fe47b8?source=cve
#!/usr/bin/env bash
set -euo pipefail
LOG=/var/log/mw-wp-form-patch-cve-2026-5436.log
log()  { echo "$(date -Iseconds)  $*" | tee -a "$LOG"; }

log "Starting CVE-2026-5436 remediation for Inc2734 MW WP Form"

# 1. Detect installed version (works for deb and rpm packages)
if command -v dpkg >/dev/null && dpkg -s mw-wp-form >/dev/null 2>&1; then
    CURRENT=$(dpkg-query -W -f='${Version}' mw-wp-form)
    PKG_MGR=apt
elif command -v rpm >/dev/null && rpm -q mw-wp-form >/dev/null 2>&1; then
    CURRENT=$(rpm -q --queryformat '%{VERSION}' mw-wp-form)
    PKG_MGR=dnf
else
    log "mw-wp-form not installed via apt or rpm; check your package manager or vendor instructions."
    exit 0
fi
log "Detected: mw-wp-form=$CURRENT (manager=$PKG_MGR)"

# 2. Backup config
BACKUP=/var/backups/mw-wp-form-$(date +%Y%m%d-%H%M)
mkdir -p "$BACKUP"
for d in /etc/mw-wp-form /etc/${pkg%%-*} ; do
    [ -d "$d" ] && cp -a "$d" "$BACKUP/" && log "Backed up $d to $BACKUP"
done

# 3. Upgrade
if [ "$PKG_MGR" = apt ]; then
    sudo apt-get update -y
    sudo apt-get install --only-upgrade -y mw-wp-form
else
    sudo dnf upgrade --security -y mw-wp-form
fi

# 4. Verify
if [ "$PKG_MGR" = apt ]; then
    NEW=$(dpkg-query -W -f='${Version}' mw-wp-form)
else
    NEW=$(rpm -q --queryformat '%{VERSION}' mw-wp-form)
fi
log "After upgrade: $NEW"
log "Done. Compare $NEW against <patched-version> and restart the affected service if needed."

If you cannot patch immediately

These are runnable hardening commands. They reduce blast radius but they are not a replacement for the vendor patch.

Rate-limit and log the affected endpoint at the reverse proxy


limit_req_zone $binary_remote_addr zone=admin:10m rate=10r/m;
location /<vulnerable-path> {
    limit_req zone=admin burst=5 nodelay;
    access_log /var/log/nginx/admin-access.log combined;
    proxy_pass http://backend;
}

How to verify the fix worked

Run the version probe again and confirm the running build matches the Fixed in row above.


dpkg -l | grep -i "mw"   # Debian/Ubuntu
rpm -qa | grep -i "mw"   # RHEL/CentOS/Rocky

Expected output: the package version should meet or exceed the patched build.

Re-run any vulnerability scanner you used previously and confirm the finding for CVE-2026-5436 has cleared. Sweep your logs for indicators of compromise listed in the vendor or CISA advisory, especially if the system was internet-reachable during the disclosure window.

Frequently asked questions

Is CVE-2026-5436 being actively exploited?