MW WP Form <= 5.0.3 - Improper Limitation of File Name to Unauthenticated Arbitrary File Deletion
Strategic Overview
- Status
- Patched in 5.0.4
- Affected Plugin
- MW WP Form
- Affected Version
<= 5.0.3- CVSS
- 7.5High
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2023-6559
At a glance
CVE-2023-6559 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the MW WP Form WordPress plugin, affecting versions <= 5.0.3. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 5.0.4; sites on affected versions should update now. Disclosed December 2023, reported by Thomas Sanzey.
Vulnerability Overview
The MW WP Form plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and including, 5.0.3. This is due to the plugin not properly validating the path of an uploaded file prior to deleting it. This makes it possible for unauthenticated attackers to delete arbitrary files, including the wp-config.php file, which can make site takeover and remote code execution possible.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in MW WP Form <= 5.0.3 takes no account at all. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For MW WP Form the fix is 5.0.4: builds <= 5.0.3 are affected, anything from 5.0.4 onward is not.
Remediation
Update to version 5.0.4, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MW WP Form 5.0.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Login Security
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in MW WP Form
- 9.8CVE-2023-6316: MW WP Form <= 5.0.1 Arbitrary File Upload
CVE-2023-6316 - 7.2CVE-2026-48871: MW WP Form <= 5.1.3 Stored Cross-Site Scripting
CVE-2026-48871 - 6.5CVE-2026-78363: MW WP Form < 5.1.5 Arbitrary Shortcode Execution
CVE-2026-78363 - 5.5CVE-2024-24804: MW WP Form <= 5.0.6 Stored Cross-Site Scripting
CVE-2024-24804 - 5.3CVE-2026-6206: MW WP Form IDOR
CVE-2026-6206 - 5.3CVE-2023-46206: MW WP Form <= 4.4.5 Missing Authorization
CVE-2023-46206 - 4.4CVE-2026-78364: MW WP Form < 5.1.6 Stored Cross-Site Scripting
CVE-2026-78364 - 4.4CVE-2026-8853: MW WP Form <= 5.1.3 Stored Cross-Site Scripting
CVE-2026-8853
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C