Skip to main content

MW WP Form CVE-2026-78363

| EUVDEUVD-2026-68991 MEDIUM
Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') (CWE-74)
2026-09-01 WPScan GHSA-224h-2cg4-2prq
4.8
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify WordPress site with MW WP Form
  2. Delivery
    Confirm echo-back feature is active
  3. Exploit
    Submit form with injected shortcode payload
  4. Execution
    Plugin reflects value through WordPress shortcode engine
  5. Persist
    Shortcode executes server-side
  6. Impact
    Extract output from post-submission response

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Input neutralization, injection prevention
Exploitation Conditions

Exploitation requires two conditions to be simultaneously true: (1) the target WordPress site must be running MW WP Form plugin version earlier than 5.1.5, and (2) the site operator must have explicitly configured the plugin to echo a submitted form field value back to the visitor in the post-submission response - this is not the default behavior and must be deliberately enabled. No authentication is required (PR:N per CVSS vector), and the attacker needs only network access to the form submission endpoint. What limits exploitation: the non-default echo-back configuration is the hard gate - sites without this feature enabled are not exploitable regardless of plugin version. Additionally, the practical impact is bounded by which WordPress shortcodes happen to be registered on the specific target site; a site with only benign shortcodes faces minimal risk even if exploited.

Impact

The CVSS 3.1 score of 4.8 (Medium) with vector AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N is well-calibrated for this vulnerability. The AC:H accurately captures the critical limiting factor: exploitation requires the site operator to have explicitly enabled the 'echo submitted value back to visitor' behavior - this is not a default configuration. Without this setting, the attack path does not exist regardless of plugin version. The PR:N reflects that no authentication is required once the condition is met. The C:L/I:L impact scoring is conservative and appropriate: the actual damage depends entirely on which shortcodes are registered on the target site - benign sites may expose only informational shortcodes, while sites with powerful plugins (e.g., shortcodes executing database queries, file operations, or user enumeration) face higher practical impact. A publicly available PoC via WPScan increases the ease of opportunistic exploitation against misconfigured instances. The vulnerability is not in CISA KEV, and the EPSS data is not provided. The combination of a gating non-default configuration and limited scope (S:U) keeps this a realistic but bounded risk. Defenders should prioritize patching sites where the echo-back feature is actively used.

Exploit ScenarioDerived

An attacker identifies a WordPress site running MW WP Form with the post-submission echo feature enabled and submits a form field containing a malicious shortcode payload such as [some-registered-shortcode param='value']. The plugin merges this value into its message template and processes it through WordPress's shortcode engine, causing the shortcode to execute server-side. Depending on registered shortcodes, the attacker could extract site configuration data, trigger information disclosure of user records, or invoke functionality exposed by other installed plugins. A publicly available PoC from WPScan simplifies identification and exploitation of vulnerable, misconfigured sites.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 01, 2026

Shortcode injection in MW WP Form WordPress plugin (versions before 5.1.5) allows unauthenticated remote attackers to execute any WordPress shortcode registered on the target site. The plugin fails to neutralize shortcode syntax in user-submitted form values before passing those values through WordPress's shortcode processing engine. A publicly available proof-of-concept exists (via WPScan), though exploitation is gated by a non-default site configuration requirement, which suppresses real-world risk despite the network-accessible attack vector.

RemediationAI

Update the MW WP Form plugin to version 5.1.5 or later, which is the vendor-released patch per the WPScan advisory at https://wpscan.com/vulnerability/0569c5f7-2001-4364-a68b-451b73f3a32a/. As an immediate compensating control for sites that cannot update immediately, disable the form configuration option that echoes submitted values back to the visitor after submission - this removes the exploitation precondition entirely and is the single most effective mitigation. If the echo-back feature is required for business purposes, consider restricting access to affected forms to authenticated users only (adding a login requirement to the page), which raises the barrier to exploitation even if the plugin version remains unpatched. Site administrators should also audit which shortcodes are registered on their WordPress installation, as the impact radius of exploitation scales with the power of available shortcodes.

Affected VersionsENISA

MW WP Form 0 <5.1.5

Affected Packages

euvd mw_wp_form fix: 5.1.5

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

MW WP Form is a WordPress plugin for building and managing contact forms. WordPress's shortcode system is a macro engine that processes bracketed tags (e.g., [gallery], [embed]) embedded in post content or plugin output. The vulnerability arises because the plugin interpolates raw user-submitted field values into a message template and then passes that composed string through do_shortcode() or equivalent WordPress processing, without first stripping shortcode syntax from user input. This is a classic second-order injection pattern - the malicious payload is stored or reflected into a context where it is later interpreted as code. The CWE is not formally assigned in the input data, but the root cause maps to CWE-94 (Improper Control of Generation of Code) or CWE-79-adjacent behavior specific to server-side shortcode evaluation. The CPE cpe:2.3:a:unknown:mw_wp_form:*:*:*:*:*:*:*:* reflects a missing vendor attribution in NVD; the plugin is developed independently for the WordPress ecosystem.

Know when Mw Wp Form gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 4.8 MEDIUM
AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
vuln.today AI 4.8 MEDIUM

AC:H reflects non-default echo-back configuration required; PR:N because no authentication needed once that condition exists; no availability impact.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

2
Patch available
Sep 01, 2026 - 09:16 EUVD
CVE Published
Sep 01, 2026 - 07:39 cve.org
MEDIUM 4.8

DescriptionCVE.org

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.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Medium
WordPress contact form plugin with meaningful install base
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

44
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +24
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.

CVE-2023-6316 CRITICAL
9.8 Jan 11

The MW WP Form plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in

CVE-2023-28409 CRITICAL
9.8 May 23

Unrestricted upload of file with dangerous type exists in MW WP Form versions v4.4.2 and earlier, which may allow a remo

CVE-2023-28408 CRITICAL
9.8 May 23

Directory traversal vulnerability in MW WP Form versions v4.4.2 and earlier allows a remote unauthenticated attacker to

CVE-2023-6559 HIGH
7.5 Dec 16

The MW WP Form plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and including, 5.0.3

CVE-2026-5436 HIGH
8.1 Apr 08

Arbitrary file manipulation in MW WP Form plugin (WordPress) versions ≤5.1.1 allows unauthenticated attackers to move se

CVE-2026-4347 HIGH
8.1 Apr 02

Arbitrary file movement in MW WP Form plugin for WordPress (all versions ≤5.1.0) allows unauthenticated remote attackers

CVE-2026-78364 LOW POC
3.5 Aug 30

Stored XSS in the MW WP Form WordPress plugin (all versions before 5.1.6) lets authenticated users holding the Editor ro

CVE-2026-96567 HIGH
7.2 Oct 02

Stored cross-site scripting in the MW WP Form plugin for WordPress (all versions up to and including 5.1.7) lets an unau

CVE-2026-48871 HIGH
7.1 Jun 15

Reflected or stored Cross-Site Scripting in the MW WP Form WordPress plugin (versions <= 5.1.3) allows remote unauthenti

CVE-2024-24804 MEDIUM
6.5 Feb 10

Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in websoudan MW WP Fo

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy