Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft URL with malicious querystring:<key> parameter
-
DeliveryDeliver link to victim via email or post
-
ExploitVictim clicks link to vulnerable form page
-
ExecutionClient-side else-branch rebuilds field from raw query string
-
ImpactInjected script executes in victim's browser session
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target page renders a Ninja Forms form that uses the {field:*} merge-tag placeholder, and that the attacker supply a matching 'querystring:<key>' / 'field:<key>' URL parameter so the server fully resolves the {field:*} placeholder, forcing the client-side else-branch to abandon the server-sanitized value and rebuild the field content from the raw query string. The decisive limiting factor is required user interaction (UI:R): a victim must be socially engineered into clicking the crafted link - there is no server-side-only, no-interaction path. Exploitation is unauthenticated (PR:N) and affects Ninja Forms versions up to and including 3.15.5. This dependence on a specific merge-tag-using form page plus mandatory victim interaction makes the realistic risk targeted rather than widespread, despite the network attack vector. |
| Impact | This is a medium-severity reflected DOM-based XSS (CVSS 6.1; CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N) in the Ninja Forms WordPress plugin. The signals are internally consistent and point to a real-but-not-emergency issue: the attack vector is network (AV:N) and unauthenticated (PR:N), but exploitation is gated by required user interaction (UI:R) - a victim must be tricked into clicking an attacker-crafted link - which sharply limits opportunistic, automatable mass exploitation and is the main reason the base score sits at medium rather than high. The vuln.today priority is 'this_month', not 'act_now' or 'emergency', aligning with the medium severity. There is no CISA KEV listing and no EPSS score was supplied in the input, so there is no evidence of active exploitation or a quantified exploitation probability; absence of these is not itself a contradiction but means the urgency rests on severity and the vendor (Wordfence) advisory rather than on observed attacks. No confirmed working exploit code was provided - the references are a vendor writeup and source/changeset links, not a PoC. Net: a legitimate issue to patch on a normal monthly cadence given the plugin's large install base, but the UI:R requirement makes it a targeted/social-engineering risk rather than a wormable, drive-by threat. |
| Exploit ScenarioDerived | An unauthenticated attacker crafts a URL for a page hosting a Ninja Forms form that uses {field:*} merge-tag placeholders, appending a malicious 'querystring:<key>' / 'field:<key>' parameter whose value contains script. The attacker sends this link to a victim (e.g., via email or a malicious post); when the victim clicks it, the client-side else-branch reconstructs the field content from the raw query string instead of the server-sanitized value, executing the injected script in the victim's browser. No public working exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 31, 2026
Reflected DOM-based cross-site scripting in the Ninja Forms WordPress plugin, affecting all versions up to and including 3.15.5, allows unauthenticated attackers to inject arbitrary web scripts that execute in a victim's browser when the crafted link is clicked (CVSS 6.1; CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N). Exploitation is conditional: the target page must render a Ninja Forms form that uses the {field:*} merge-tag placeholder, and the attacker must supply a matching 'querystring:<key>'/'field:<key>' URL parameter so the server fully resolves the placeholder, after which the client-side else-branch abandons the server-sanitized value and reconstructs the field content from the raw query string. There is no server-side-only, no-interaction path - the required victim interaction keeps realistic risk targeted rather than widespread, and no public exploit was identified at time of analysis.
RemediationAI
No tagged patched release is confirmed in the available data; the fix is present as an upstream changeset (https://plugins.trac.wordpress.org/changeset/3749135/ninja-forms/trunk/assets/js/min/front-end.js), so treat this as 'Upstream fix available (PR/commit); released patched version not independently confirmed' and verify the current plugin version against the WordPress.org plugin page (https://wordpress.org/plugins/ninja-forms/) or the Wordfence advisory before relying on an upgrade. Where an immediate release is unavailable, compensating controls are to remove or avoid {field:*} merge-tag placeholders on any form rendered on publicly reachable pages - this eliminates the else-branch path that rebuilds field content from the raw query string, at the cost of losing dynamic field prefill/display functionality in those forms - and, until patched, to treat crafted links containing 'querystring:<key>' or 'field:<key>' parameters against such forms as hostile. Applying the upstream changeset manually is an option but carries the side effect of an unverified modification against a released version that must be re-applied or reconciled at the next official update.
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
The issue is a CWE-79 cross-site scripting flaw with a DOM-based execution path in a WordPress plugin. Ninja Forms supports merge tags, and the {field:*} placeholder is resolved server-side (the merge-tag handling is implemented in includes/MergeTags/Other.php, referenced at line 41 of the 3.15.4 tag), with rendered field markup coming from includes/Templates/fields-html.html and client-side behavior handled by assets/js/min/front-end.js. When a page renders a form containing a {field:*} placeholder and the attacker supplies a matching 'querystring:<key>'/'field:<key>' parameter, the server fully resolves the placeholder; the client-side else-branch in front-end.js then discards the server-sanitized value and rebuilds the field content from the raw query string, so insufficient input sanitization combined with insufficient output escaping yields script execution in the victim's browser. The CVSS scope-changed rating (S:C) reflects that the injected script runs in the context of the hosting WordPress site beyond the vulnerable component itself, with low confidentiality and integrity impact and no availability impact. The trigger depends on the specific form configuration described above; whether other form or parameter combinations are also exploitable is not described in the available sources.
Know when Wordpress Plugin 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:R/S:C/C:L/I:L/A:N
Unauthenticated reflected XSS over the network (AV:N/PR:N) that requires a victim to click a crafted link (UI:R); script runs in the browser security context (S:C) with limited C/I impact and no availability effect.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Ninja Forms - Contact Form Builder with Calculators, Quizzes, Signatures & AI Form Builder plugin for WordPress is vulnerable to Reflected DOM-Based Cross-Site Scripting via 'querystring:<key>' URL Parameter in all versions up to, and including, 3.15.5 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. This bypass is triggered when an attacker supplies a matching field:<key> URL parameter that causes the server to fully resolve the {field:*} placeholder, forcing the client-side else-branch to abandon the server-sanitized value and reconstruct field content from the raw query string.
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
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The AI Engine WordPress plugin through version 3.1.3 exposes Bearer Token values through the /mcp/v1/ REST API endpoint
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
EUVD-2026-114704
GHSA-qf5g-wf7g-22vp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB