Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Arbitrary File Move in MW WP Form for WordPress

IdentifiersCVE-2026-4347CWE-22· Improper Limitation of a Pathname…

CVE-2026-4347 is an arbitrary file moving vulnerability in the MW WP Form plugin for WordPress affecting all versions up to and including 5.1.0. The issue is caused by insufficient file path validation in the generate_user_filepath and move_temp_file_to_upload_dir functions. An unauthenticated attacker can abuse the vulnerable file-handling logic to cause arbitrary files on the server to be moved. The provided context specifically notes that moving a sensitive file such as wp-config.php can turn the issue into remote code execution. The flaw is only reachable in deployments where a form includes a file upload field and the plugin option for saving inquiry data in the database is enabled.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows an unauthenticated attacker to move arbitrary files on the server. This can compromise confidentiality, integrity, and availability depending on which file is moved. In the documented worst case, moving a sensitive file such as wp-config.php can lead to remote code execution. The supplied CVSS context also indicates high impact across confidentiality, integrity, and availability.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce exposure by disabling or removing file upload fields from MW WP Form forms and disabling the "Saving inquiry data in database" option, since the vulnerability is only exploitable when both conditions are present. Restrict public access to vulnerable forms where feasible and monitor for unexpected movement of sensitive files such as wp-config.php.

Remediation

Patch, then assume compromise.

Update the MW WP Form plugin to a version newer than 5.1.0. The provided context identifies all versions up to and including 5.1.0 as affected, so remediation is to deploy a fixed release that addresses the insufficient file path validation in generate_user_filepath and related file-moving logic.
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity4

Community discussion across Reddit, Mastodon, and other social sources.