HomeWordPress vulnerabilitiesMW WP Form
MW WP Form vulnerabilities
MW WP Form has 9 known vulnerabilities in this database. The most recent published record is dated 2 Oct 2026.
- Known vulnerabilities
- 9
- Active installs
- 200,000+
- Latest version
- 5.1.8
- Last updated
- 27 Sep 2026
- Most recent
- 2 Oct 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2026-96567 | High 7.2 | Up to 5.1.7 | Fixed in a later version (latest 5.1.8) | 5 d ago |
| Security weakness CVE-2026-78363 | Medium 4.8 | Before 5.1.5 | Fixed in 5.1.5 | 1 Sep 2026 |
| Cross-site scripting (XSS) CVE-2026-78364 | Low 3.5 | Before 5.1.6 | Fixed in 5.1.6 | 30 Aug 2026 |
| Cross-site scripting (XSS) CVE-2026-8853 | Medium 4.4 | Up to 5.1.3 | Fixed in a later version (latest 5.1.8) | 10 Jun 2026 |
| Broken access control CVE-2026-6206 | Medium 5.3 | Up to 5.1.2 | Fixed in a later version (latest 5.1.8) | 14 May 2026 |
| Remote code execution CVE-2026-5436 | High 8.1 | Up to 5.1.1 | Fixed in a later version (latest 5.1.8) | 8 Apr 2026 |
| Remote code execution CVE-2026-4347 | High 8.1 | Up to 5.1.0 | Fixed in a later version (latest 5.1.8) | 2 Apr 2026 |
| Remote code execution CVE-2023-6316 | Critical 9.8 | Up to 5.0.1 | Fixed in a later version (latest 5.1.8) | 11 Jan 2024 |
| Remote code execution CVE-2023-6559 | High 7.5 | Before 5.0.4 | Fixed in 5.0.4 | 16 Dec 2023 |
Read the published descriptions
- CVE-2026-96567, 2 Oct 2026
- The MW WP Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'post_id' parameter in all versions up to, and including, 5.1.7 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The CSRF gate protecting form submission (MW_WP_Form_Csrf) is bypassable by any unauthenticated visitor who first loads the public form page to obtain a valid double-submit cookie, leaving no effective barrier to storing malicious payloads. CVE record
- CVE-2026-78363, 1 Sep 2026
- The MW WP Form WordPress plugin before 5.1.5 does not prevent shortcodes in user-submitted values from being executed when it merges those values into a message that it later processes for shortcodes, allowing unauthenticated users to run any shortcode registered on the site. Exploitation requires the site to have been configured to echo a submitted value back to the visitor after submission. CVE record
- CVE-2026-78364, 30 Aug 2026
- The MW WP Form WordPress plugin before 5.1.6 does not sanitise and escape some of its form settings before outputting them back in an admin dashboard page, which could allow users with a role as low as Editor to perform Stored Cross-Site Scripting attacks against high privilege users such as admin. CVE record
- CVE-2026-8853, 10 Jun 2026
- The MW WP Form plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'memo' parameter in all versions up to, and including, 5.1.3 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with editor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Because the memo value is stored via update_post_meta() rather than wp_insert_post(), WordPress's built-in kses and unfiltered_html protections do not apply, allowing attackers to break out of the textarea element via injected closing tags regardless of role-based content filtering. CVE record
- CVE-2026-6206, 14 May 2026
- The MW WP Form plugin for WordPress is vulnerable to Information Exposure in all versions up to, and including, 5.1.2 via the _get_post_property_from_querystring() function due to insufficient restrictions on which posts can be included. This makes it possible for unauthenticated attackers to extract data from password protected, private, or draft posts that they should not have access to. CVE record
- CVE-2026-5436, 8 Apr 2026
- 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. CVE record
- CVE-2026-4347, 2 Apr 2026
- 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. CVE record
- CVE-2023-6316, 11 Jan 2024
- The MW WP Form plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the '_single_file_upload' function in versions up to, and including, 5.0.1. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. CVE record
- CVE-2023-6559, 16 Dec 2023
- 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. CVE record
What to do if you run MW WP Form
If you run MW WP Form, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new MW WP Form vulnerabilities
Free. We email you when a new vulnerability is published for MW WP Form, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.