Skip to main content

WPForms Lite CVE-2026-84744

| EUVDEUVD-2026-88098 MEDIUM
Code Injection (CWE-94)
2026-09-28 WPScan GHSA-7fm6-hmq5-pxwv
6.5
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

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

  1. Access
    Submit form field containing shortcode delimiters
  2. Exploit
    Value rendered back without sanitization
  3. Execution
    Registered shortcode executes on server
  4. Impact
    Read non-public post attachment details

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

No special conditions - remote unauthenticated exploitation against default configurations of WPForms Lite (versions 1.5.0.1 through 2.0.2) via any public form that echoes submitted field values back into the rendered form. Exploitation requires only that a WPForms form is present and reachable, and that the site has shortcodes registered whose execution yields useful effect (e.g. attachment/gallery shortcodes referencing non-public posts); the concrete impact is therefore bounded by which shortcodes exist on the target, and disclosure is limited to attachment details rather than full content, which caps confidentiality impact at Low.

Impact

The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N = 6.5 Medium) is internally consistent with the description: an unauthenticated, network-reachable, low-complexity attack requiring no user interaction, yielding limited confidentiality and integrity impact. This is a shortcode-injection flaw, not memory-corruption RCE, so the 'RCE' tag overstates it - arbitrary execution of already-registered shortcodes is not equivalent to arbitrary system code execution, and the real-world impact is bounded by which shortcodes exist on the target site (information disclosure of non-public post attachment details being the concrete demonstrated effect). Publicly available exploit code exists (WPScan), which raises practical risk, but there is no EPSS score, no CISA KEV listing, and no SSVC framework data supplied, so exploitation is 'known-possible' rather than 'known-active'. The combination of a huge install base (WPForms Lite), unauthenticated reachability, and public POC makes this a genuinely elevated-priority patching item despite the mid-range CVSS, though it is not a critical takeover primitive. Note: CWE is 'N/A' in the input and CPE vendor is the placeholder 'unknown', so classification metadata is incomplete and should be corrected against the WPScan advisory.

Exploit ScenarioDerived

An unauthenticated visitor submits a WPForms form with a field value containing WordPress shortcode delimiters (e.g. [gallery ...] or another registered shortcode); the plugin writes the raw value back into the rendered form without stripping the delimiters, so the shortcode executes in the site context and can, for example, disclose attachment details of non-public posts. Public exploit code is available via WPScan, lowering the skill barrier.

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 28, 2026

Unauthenticated shortcode injection in WPForms Lite (versions 1.5.0.1 through 2.0.2) lets remote attackers execute arbitrary registered WordPress shortcodes by submitting form field values that the plugin echoes back into the rendered form without stripping shortcode delimiters. Publicly available exploit code exists via the WPScan advisory, and the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N (6.5 Medium) confirms low-complexity, no-user-interaction exploitation. Impact is bounded by the shortcodes present on the target; successful exploitation can disclose attachment details of non-public posts and modify rendered form output, but does not by itself grant full remote code execution.

RemediationAI

No fixed version is specified in the provided data; the WPScan advisory and vendor should be consulted for a patched WPForms Lite release, and administrators should upgrade to the latest available version beyond 2.0.2 when it becomes available. If a patch is not yet installed, disable the WPForms Lite plugin until it can be updated, or remove public forms that echo user-submitted values. Compensating controls include blocking [ and ] characters in WPForms submissions at the WAF or application level, with the trade-off that legitimate shortcode usage in forms will break; restricting form access to authenticated users; and auditing or disabling registered shortcodes that reference non-public posts' attachments (e.g., gallery or attachment shortcodes) if they are not required. Note that disabling the plugin removes all WPForms functionality, so evaluate the operational impact. Reference: https://wpscan.com/vulnerability/99c4a9fc-114e-4d39-80aa-0e9544125794/.

Affected VersionsENISA

WPForms 1.5.0.1 <2.0.2.1

Affected Packages

euvd wpforms fix: 2.0.2.1

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

WordPress shortcodes are macros in square brackets that are processed by do_shortcode() when content is rendered. WPForms Lite up to 2.0.2 fails to sanitize or escape the shortcode delimiters ([ and ]) in user-submitted field values before those values are written back into the form markup. If the site has shortcodes registered (e.g., attachment, gallery, or other plugins' shortcodes), the echoed value is interpreted and executed when the form is rendered. This is not a memory-corruption or direct RCE issue; it is a context-dependent shortcode injection that hinges on which shortcodes are active and whether they expose data such as attachment details from non-public posts. The CPE entry (cpe:2.3:a:unknown:wpforms:*:*:*:*:*:*:*:*) reflects a WordPress plugin with an unidentified vendor mapping, and no CWE is assigned in the provided data, but the root cause is improper neutralization of shortcode delimiters in user-controlled input. Although a tag lists RCE, the independent assessment treats this as shortcode injection with bounded impact rather than direct arbitrary code execution.

Know when Wpforms 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 6.5 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
vuln.today AI 6.5 MEDIUM

Unauthenticated network form submission with no interaction (AV:N/AC:L/PR:N/UI:N); shortcode execution and attachment-detail leakage give limited C:L/I:L, no availability impact, scope unchanged.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/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
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

2
Patch available
Sep 28, 2026 - 08:01 EUVD
CVE Published
Sep 28, 2026 - 06:19 cve.org
MEDIUM 6.5

DescriptionCVE.org

The WPForms Lite WordPress plugin from 1.5.0.1 to 2.0.2 does not remove shortcode delimiters from submitted field values before writing them back into the rendered form, allowing unauthenticated users to execute arbitrary shortcodes registered on the site and read the details of attachments belonging to non-public posts.

Threat Intelligence Overview

EPSS Score
0.2%
Top 93% exploitable
Prevalence
High
WPForms Lite is among the most widely deployed WordPress form plugins (millions of installs)
Exploit
POC
Public exploit code exists
Data Quality
4 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
Out-of-Cycle
Exploitation
None
System Exposure· derived
Open
Automatable
Yes
Human Impact· derived
High
Technical Impact
Partial

Priority Score

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

Attack Technique

Code Injection CRITICAL

Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

CVE-2022-3574 CRITICAL POC
9.8 Nov 14

The WPForms Pro WordPress plugin before 1.7.7 does not validate its form data when generating the exported CSV, which co

CVE-2019-25145 HIGH POC
7.2 Jun 07

The Contact Form & SMTP Plugin by PirateForms plugin for WordPress is vulnerable to HTML injection in the ‘public/class-

CVE-2026-74991 MEDIUM POC
6.8 Sep 24

Unauthenticated attackers can force full refunds and immediate subscription cancellations on WordPress sites running the

CVE-2024-11272 MEDIUM POC
6.1 Mar 25

The Contact Form & SMTP Plugin for WordPress by PirateForms WordPress plugin before 2.6.0 does not sanitise and escape s

CVE-2020-36919 MEDIUM POC
6.1 Jan 13

WPForms 1.7.8 contains a cross-site scripting vulnerability in the slider import search feature and tab parameter. Attac

CVE-2020-10385 MEDIUM POC
5.4 Mar 24

A stored cross-site scripting (XSS) vulnerability exists in the WPForms Contact Form (aka wpforms-lite) plugin before 1.

CVE-2024-11223 MEDIUM POC
4.7 Dec 26

The WPForms WordPress plugin before 1.9.2.3 does not sanitise and escape some of its settings, which could allow high pr

CVE-2024-7056 LOW POC
3.5 Nov 25

The WPForms WordPress plugin before 1.9.1.6 does not sanitise and escape some of its settings, which could allow high pr

CVE-2026-18409 HIGH
7.2 Aug 21

Stored Cross-Site Scripting in WPForms Pro for WordPress (all versions through 2.0.0.2) allows unauthenticated remote at

CVE-2024-11205 MEDIUM
6.5 Dec 10

The WPForms plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on

CVE-2024-13403 MEDIUM
6.4 Feb 04

The WPForms - Easy Form Builder for WordPress - Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vu

CVE-2023-30500 MEDIUM
6.1 Jun 22

Unauth. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low at

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