WordPress security changelog
MEDIUM CVE-2026-8853 Deferred

MW WP Form: Cross-site scripting

MW WP Form is affected by cross-site scripting. Exploitation requires at least editor-level access. Injected script can execute in the affected site's origin when the vulnerable output is viewed. The published affected range is <= 5.1.3.

CVE / CNA score 4.4 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
MW WP Form
Plugin slug
mw-wp-form
Affected
<= 5.1.3
Safe version
> 5.1.3
Published
Jun 10, 2026
Weakness
CWE-79 — Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

This CVE was published Jun 10, 2026 and is one of 9 known issues for this plugin.

What to do

Update, patch or deactivate.

Update MW WP Form to a release after 5.1.3, or disable and remove it until a fixed version is available.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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 / CNA vector: CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:L/I:L/A:N

References

Primary and upstream sources