CVE-2026-5436 Details
Description
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(). During form processing, regenerate_upload_file_keys() iterates over these keys and calls generate_user_filepath() with the attacker-supplied key as the $name argument — the key survives validation because the targeted file (e.g., wp-config.php) genuinely exists at the absolute path. The _get_attachments() method then re-reads the same surviving keys and passes the resolved file path to move_temp_file_to_upload_dir(), which calls rename() to move the file into the uploads folder. 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.
A vulnerability allowing arbitrary file movement has been identified in the MW WP Form plugin for WordPress, affecting all versions through 5.1.1. The issue arises from inadequate validation of the '$name' parameter, which is the upload field key. This parameter is passed to the 'generate_user_file_dirpath()' function, where it is manipulated by WordPress's 'path_join()' function, returning absolute paths without modification and ignoring the intended base directory. The vulnerability can be exploited by injecting an attacker-controlled key via the 'mwf_upload_files[]' POST parameter. This key is then processed by the plugin's Data model, specifically through the '_set_request_valiables()' method. During form processing, the 'regenerate_upload_file_keys()' function iterates over the uploaded file keys and calls 'generate_user_filepath()' with the injected key. The key bypasses validation because the targeted file, such as 'wp-config.php', exists at the absolute path. Subsequently, the '_get_attachments()' method retrieves the same keys, resolves the file path, and uses 'move_temp_file_to_upload_dir()' to transfer the file to the uploads directory. This vulnerability allows unauthenticated attackers to move arbitrary files on the server, potentially leading to remote code execution if sensitive files like 'wp-config.php' are targeted.
Users are advised to update the MW WP Form plugin to version 5.1.2 or later, where this vulnerability has been patched.
Metrics
CVSS 4.0 Severity and Vector Strings:
CVSS 3.x Severity and Vector Strings:
No data available for CVSS Version 2.0 on this CVE.
Volerion
Assessed Apr 8, 2026CISA-ADP
Assessed Apr 10, 2026References to Advisories, Solutions, and Tools
By selecting these links, you will be leaving this site. These are references gathered from the official CVE record and are not endorsed by Volerion.
Weakness Enumeration
| CWE-ID | CWE Name | Source |
|---|---|---|
| CWE-22 | Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') | [email protected] |
Affected Products
| Product | Versions |
|---|---|
| MW WP Form | <= 5.1.1 (semver) |
CPE
Remediation
| |
Change History
4 change records found show changes
| Date | Action | Recorded By |
|---|---|---|
| Jul 24, 2026 | CVE Translated | [email protected] |
| Jun 17, 2026 | CVE Modified | [email protected] |
| Jun 17, 2026 | CVE Modified | CISA-ADP |
| Apr 8, 2026 | New CVE Received | [email protected] |
Volerion