Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSubmit form field containing shortcode delimiters
-
ExploitValue rendered back without sanitization
-
ExecutionRegistered shortcode executes on server
-
ImpactRead 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. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – 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
Affected Packages
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
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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.
Primary rating from Vendor (WPScan).
CVSS VectorVendor: WPScan
Lifecycle Timeline
2DescriptionCVE.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
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
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.
The WPForms Pro WordPress plugin before 1.7.7 does not validate its form data when generating the exported CSV, which co
The Contact Form & SMTP Plugin by PirateForms plugin for WordPress is vulnerable to HTML injection in the ‘public/class-
Unauthenticated attackers can force full refunds and immediate subscription cancellations on WordPress sites running the
The Contact Form & SMTP Plugin for WordPress by PirateForms WordPress plugin before 2.6.0 does not sanitise and escape s
WPForms 1.7.8 contains a cross-site scripting vulnerability in the slider import search feature and tab parameter. Attac
A stored cross-site scripting (XSS) vulnerability exists in the WPForms Contact Form (aka wpforms-lite) plugin before 1.
The WPForms WordPress plugin before 1.9.2.3 does not sanitise and escape some of its settings, which could allow high pr
The WPForms WordPress plugin before 1.9.1.6 does not sanitise and escape some of its settings, which could allow high pr
Stored Cross-Site Scripting in WPForms Pro for WordPress (all versions through 2.0.0.2) allows unauthenticated remote at
The WPForms plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on
The WPForms - Easy Form Builder for WordPress - Contact Forms, Payment Forms, Surveys, & More plugin for WordPress is vu
Unauth. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low at
EUVD-2026-88098
GHSA-7fm6-hmq5-pxwv
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB