PT-2026-31452 · Inc2734 · Mw Wp Form
Sander Horsman
·
Published
2026-04-08
·
Updated
2026-04-08
·
CVE-2026-5436
CVSS v3.1
8.1
High
| Vector | AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H |
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.
Fix
Path traversal
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Mw Wp Form