CVE-2026-18409
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe WPForms Pro plugin for WordPress is vulnerable to Stored Cross-Site Scripting via Single Line Text and Paragraph Text Field Values in all versions up to, and including, 2.0.0.2 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. The exploit relies on the plugin's own wp_kses_allowed_html filter widening the 'post' allowlist to permit iframe elements with a data-src attribute, which is not on WordPress's URI-attribute sanitization list, allowing a javascript: URI stored in data-src to survive kses processing and subsequently be promoted to a live src attribute by the bundled admin script view-entry.min.js.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysisUntrusted input is placed into a web page without being neutralised, so an attacker's markup or script executes in another user's browser. That can hijack sessions, capture keystrokes, or silently perform actions as the victim. Fixing it properly means context-aware output encoding everywhere data meets HTML, backed by a content-security policy as a second line of defence.
General guidance for the cross-site scripting (xss) class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedWPForms Pro version later than 2.0.0.2 (contact vendor for exact fixed release)
- Check the current version of WPForms Pro plugin installed on your WordPress site
- Navigate to WPForms > Plugins in the WordPress admin dashboard
- If the installed version is 2.0.0.2 or earlier, update to the latest version of WPForms Pro
- Verify the update was successful and test that form submissions work correctly
- Review form entries in the admin panel to ensure the vulnerability is mitigated
Generated from the published advisory — verify against the referenced sources before acting.
There is no version to upgrade to and no patch to apply. Every affected install stays exposed until the vendor ships a fix — or somebody else builds one.
Free. We build fixes in the order the community asks for them — and we’ll tell you the moment this one lands.
We develop and verify an original fix where the vendor hasn’t, from $3,100. Deployed to your staging first — never straight to production.
Scope it with usSee what else the community needs solved on the solutions-needed board.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-18409 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesThis vulnerability exposes a two-stage execution path that neither server-side sanitization nor client-side code alone creates — only their interaction does. WPForms widened its wp_kses_allowed_html allowlist to support iframe elements in form submissions. The problem: kses permits any content in the data-src attribute because it's not a URI-validated attribute. When view-entry.min.js — a legacy admin script — promotes data-src to src in the live DOM, a javascript: URI that survived server-side filtering executes in the browser. The fix wasn't just tightening the allowlist. Check whether your deployment has the patch: look for removal of iframe from the custom kses configuration, or better, verify that data-src attributes are stripped or neutralized before client-side rendering in admin pages. If you're on an unpatched version, treat any form submission containing iframe HTML as potentially malicious — the payload executes when an admin views the entry in the WPForms admin panel. The deeper lesson is that server-side content filtering cannot be your only defense against DOM-based execution. Any client-side code that reads kses-permitted attributes and promotes them to active DOM attributes is now participating in your security posture — whether the developers intended it or not. Audit admin JavaScript files for attribute-promotion patterns (data-* to active attributes), and treat that code as security-critical, not UX polish. The pattern of allowlist widening → client-side attribute promotion → javascript: execution has been reproduced across dozens of WordPress plugins. It's a known attack surface with commoditized exploit tooling, and WPForms' millions of active installations make it a high-value target. The gap between CVE publication and ecosystem-wide patching is your exposure window — automate your update pipeline for this one.
Practitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-18409 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data