# CVE-2026-4347: MW WP Form <= 5.1.0 - Unauthenticated Arbitrary File Move via move_temp_file_to_upload_dir

> Unauthenticated attackers can move arbitrary files on the server, potentially leading to remote code execution, in the MW WP Form WordPress plugin.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Apr 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-2mhf-8wh4-g2p3

## What is CVE-2026-4347?

CVE-2026-4347 is a high-severity path traversal vulnerability in inc2734 MW WP Form, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The MW WP Form plugin for WordPress is vulnerable to arbitrary file moving due to insufficient file path validation via the 'generate_user_filepath' function and the 'move_temp_file_to_upload_dir' function in all versions up to, and including, 5.1.0. This makes it possible for unauthenticated attackers to move arbitrary files on the server, which can easily lead to remote code execution when the right file is moved (such as wp-config.php). The vulnerability is only exploitable if a file upload field is added to the form and the “Saving inquiry data in database” option is enabled.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-4347?


## How do I fix CVE-2026-4347?

No fix has been published for CVE-2026-4347 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-4347 being exploited?

There is no known exploitation of CVE-2026-4347 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-4347 and fix it if it is affected.

What it is: CVE-2026-4347 is a high-severity path traversal vulnerability in inc2734 MW WP Form, published on 2 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-4347 in the wild and no public exploit code.

Affected product: inc2734 MW WP Form. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-4347/ (Markdown: https://insights.sbomify.com/CVE-2026-4347/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-4347
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-4347
- OSV: https://osv.dev/vulnerability/CVE-2026-4347

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-4347/
Summaries are generated and may contain mistakes; the official description above is the record.