CVE-2026-5436
Awaiting Analysis Awaiting Analysis - Queue
Arbitrary File Move in MW WP Form Plugin Enables RCE

Publication date: 2026-04-08

Last updated on: 2026-04-08

Assigner: Wordfence

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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-04-08
Last Modified
2026-04-08
Generated
2026-05-07
AI Q&A
2026-04-09
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
mw_wp_form mw_wp_form to 5.1.1 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-22 The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The MW WP Form plugin for WordPress has a vulnerability called Arbitrary File Move/Read in all versions up to 5.1.1. This happens because the plugin does not properly validate the $name parameter, which is used to generate file paths. An attacker can supply a specially crafted key through the mwf_upload_files[] POST parameter that bypasses validation and points to an absolute file path on the server.

During form processing, the plugin processes these keys and moves files from their original locations to the uploads folder. Because the attacker can specify any file path, they can move critical files like wp-config.php. This vulnerability can be exploited without authentication but requires that a file upload field is present in the form and that the option to save inquiry data in the database is enabled.


How can this vulnerability impact me? :

This vulnerability allows unauthenticated attackers to move arbitrary files on the server. By moving sensitive files such as wp-config.php into the uploads directory, attackers can potentially execute remote code on the server.

The impact includes full compromise of the affected WordPress site, leading to data breaches, site defacement, or further attacks on the hosting environment.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

The vulnerability allows unauthenticated attackers to move arbitrary files on the server, potentially leading to remote code execution. This can result in unauthorized access to sensitive data or disruption of service.

Such unauthorized access and potential data breaches could negatively impact compliance with data protection regulations like GDPR and HIPAA, which require safeguarding personal and sensitive information against unauthorized access and ensuring system integrity.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, you should ensure that you are not using any version of the MW WP Form plugin up to and including 5.1.1, as these versions are vulnerable.

Additionally, avoid enabling the "Saving inquiry data in database" option if you have a file upload field added to your form, since the vulnerability requires both conditions to be exploitable.

Applying updates or patches from the plugin developer once available is also recommended to fix the insufficient validation issue.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart