Plugins · mw-wp-form · data as of 2026-11-04
Is MW WP Form safe? Known vulnerabilities and latest version
- Latest version
- 5.1.8
- Last updated
- 2026-09-27
- Active installs
- 200,000+
- Known issues on record
- 15
- Unpatched in latest
- 0
- Tested up to WP
- 6.4.14 · PHP 8.0+
MW WP Form is shortcode base contact form plugin. This plugin have many features. For example you can use many validation rules, inquiry data saving, … — by Webの相談所
What to do
- Update to the latest version (5.1.8). Anything older than 5.1.8 has at least one known issue listed below. Dashboard → Updates, or Plugins → “update now”.
- If you cannot update right away, deactivate it until you can.
- Turn on auto-updates for it: Plugins → “Enable auto-updates” on its row.
- If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan.
With WP-CLI: wp plugin get mw-wp-form --field=version shows what you run; wp plugin update mw-wp-form updates it.
Check your version
Known vulnerabilities
15 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.
medium 5.3 CVE-2026-92086 · published 2026-10-29
Information disclosure in MW WP Form (5.1.7 and older)
- Affected
- 5.1.7 and older
- Fixed in
- 5.1.8 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
The MW WP Form plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.1.7 via the 'post_id' parameter. This makes it possible for unauthenticated attackers to extract personally identifiable information from other users' form inquiry records, including submitted names, email addresses, and free-text message bodies, by enumerating sequential post IDs. Exploitation requires the targeted form to have the querystring setting enabled, but this is a standard documented feature of the plugin.
high 7.2 CVE-2026-96567 · published 2026-10-02
Cross-site request forgery (CSRF) in MW WP Form (5.1.7 and older)
- Affected
- 5.1.7 and older
- Fixed in
- 5.1.8 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-96567Wordfence advisoryCode change (fix)Plugin source
medium 4.8 CVE-2026-78363 · published 2026-09-01
Content injection in MW WP Form (older than 5.1.5)
- Affected
- older than 5.1.5
- Fixed in
- 5.1.5
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by WPScan
Details from the advisory
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.
low 3.5 CVE-2026-78364 · published 2026-08-30
Stored cross-site scripting (XSS) in MW WP Form (older than 5.1.6)
- Affected
- older than 5.1.6
- Fixed in
- 5.1.6
- Access needed (per CVSS)
- Needs an admin-level account; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by CISA ADP
Details from the advisory
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.
high 7.1 CVE-2026-48871 · published 2026-06-15
Cross-site scripting (XSS) in MW WP Form (5.1.3 and older)
- Affected
- 5.1.3 and older
- Fixed in
- 5.1.4
- Access needed (per CVSS)
- No login needed; someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Unauthenticated Cross Site Scripting (XSS) in MW WP Form <= 5.1.3 versions.
medium 4.4 CVE-2026-8853 · published 2026-06-10
Stored cross-site scripting (XSS) in MW WP Form (5.1.3 and older)
- Affected
- 5.1.3 and older
- Fixed in
- 5.1.4 *
- Access needed (per CVSS)
- Needs an admin-level account
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-8853Wordfence advisoryCode change (fix)Plugin source
medium 5.3 CVE-2026-6206 · published 2026-05-14
Information disclosure in MW WP Form (5.1.2 and older)
- Affected
- 5.1.2 and older
- Fixed in
- 5.1.3 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-6206Wordfence advisoryCode change (fix)github.com
high 8.1 CVE-2026-5436 · published 2026-04-08
Remote code execution in MW WP Form (5.1.1 and older)
- Affected
- 5.1.1 and older
- Fixed in
- 5.1.2 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
NVD CVE-2026-5436Wordfence advisoryCode change (fix)github.comPlugin source
high 8.1 CVE-2026-4347 · published 2026-04-02
Remote code execution in MW WP Form (5.1.0 and older)
- Affected
- 5.1.0 and older
- Fixed in
- 5.1.1 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Wordfence
Details from the advisory
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.
medium 5.3 CVE-2023-46206 · published 2025-01-02
Missing authorization check in MW WP Form (4.4.5 and older)
- Affected
- 4.4.5 and older
- Fixed in
- 5.0.0
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by Patchstack
Details from the advisory
Missing Authorization vulnerability in Webの相談所 MW WP Form mw-wp-form allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects MW WP Form: from n/a through <= 4.4.5.
medium 5.4 CVE-2024-24804 · published 2024-02-10
Stored cross-site scripting (XSS) in MW WP Form (5.0.6 and older)
- Affected
- 5.0.6 and older
- Fixed in
- 5.0.7 *
- Access needed (per CVSS)
- Needs a low-level account (e.g. subscriber); someone on the site has to click a link or open a page
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in websoudan MW WP Form allows Stored XSS.This issue affects MW WP Form: from n/a through 5.0.6.
critical 9.8 CVE-2023-6316 · published 2024-01-11
Arbitrary file upload in MW WP Form (5.0.1 and older)
- Affected
- 5.0.1 and older
- Fixed in
- 5.0.2 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
NVD CVE-2023-6316Wordfence advisoryCode change (fix)Plugin source
critical 9.8 CVE-2023-6559 · published 2023-12-16
Arbitrary file deletion in MW WP Form (5.0.3 and older)
- Affected
- 5.0.3 and older
- Fixed in
- 5.0.4 *
- Access needed (per CVSS)
- No login needed
- Range from
- CVE record (the advisory publisher) · score by NVD
Details from the advisory
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.
critical 9.8 CVE-2023-28408 · published 2023-05-23
Path traversal / file read in MW WP Form (4.4.2 and older)
- Affected
- 4.4.2 and older
- Fixed in
- 4.4.3 *
- Access needed (per CVSS)
- No login needed
- Range from
- NVD analysis · score by NVD
Details from the advisory
Directory traversal vulnerability in MW WP Form versions v4.4.2 and earlier allows a remote unauthenticated attacker to alter the website or cause a denial-of-service (DoS) condition, and obtain sensitive information depending on settings.
critical 9.8 CVE-2023-28409 · published 2023-05-23
Arbitrary file upload in MW WP Form (4.4.2 and older)
- Affected
- 4.4.2 and older
- Fixed in
- 4.4.3 *
- Access needed (per CVSS)
- No login needed
- Range from
- NVD analysis · score by NVD
Details from the advisory
Unrestricted upload of file with dangerous type exists in MW WP Form versions v4.4.2 and earlier, which may allow a remote unauthenticated attacker to upload an arbitrary file.
Recent activity
- 2026-09-27 — latest release on wordpress.org (5.1.8).
- 2026-10-29 — Information disclosure disclosed (CVE-2026-92086), fixed in 5.1.8.
- 2026-10-02 — Cross-site request forgery (CSRF) disclosed (CVE-2026-96567), fixed in 5.1.8.
- 2026-09-01 — Content injection disclosed (CVE-2026-78363), fixed in 5.1.5.
Get an email when MW WP Form has a new vulnerability
Free. We check the CVE feeds every day and email you only when a new issue for MW WP Form (mw-wp-form) is published or a fix ships. Unsubscribe in one click.
Browse vulnerabilities
- Published this week
- Unpatched in the latest version
- By type of vulnerability
- Plugins by Webの相談所 (2 tracked)
Types found in this plugin: Cross-site scripting (XSS) (4) · Sensitive data exposure (2) · Remote code execution (2) · Arbitrary file upload (2) · Cross-site request forgery (CSRF) (1) · Content injection (1) · Missing authorization (1) · Arbitrary file deletion (1) · Path traversal and file read (1)
Where this data comes from
- Version, last update, installs: wordpress.org/plugins/mw-wp-form (Plugins API), fetched 2026-11-04.
- Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
- Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.
Badge for your site or docs (states facts with a date, not a verdict):
<a href="https://laskyr.com/plugins/mw-wp-form"><img src="https://laskyr.com/plugins/mw-wp-form/badge.svg" alt="MW WP Form vulnerability status"></a>