CVE-2026-5063
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 NEX-Forms – Ultimate Forms Plugin for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via POST parameter key names in the submit_nex_form() function in versions up to, and including, 9.1.11 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.
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 analysis · high confidenceThe NEX-Forms WordPress plugin up to version 9.1.11 contains a stored XSS vulnerability in the submit_nex_form() function. Unauthenticated attackers can inject malicious JavaScript via POST parameter key names due to insufficient input sanitization and lack of output escaping. The injected scripts persist and execute whenever users access pages containing the affected form data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
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
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify NEX-Forms plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and locate NEX-Forms. Note the version number displayed under the plugin name.Affected if Plugin is not installed or has been removed entirely (not vulnerable)
-
Compare installed version to affected rangeCheck if the installed version is 9.1.11 or lower. The vulnerability affects versions up to 9.1.11.Affected if Installed version is 9.1.11 or lower (vulnerable to this CVE)
-
Confirm forms are publicly accessibleCheck if any NEX-Forms forms are embedded on publicly accessible pages (pages visible to unauthenticated visitors). Since the flaw is exploitable via unauthenticated POST requests, any published form could be targeted.Affected if Forms are published and accessible to unauthenticated users (exploitation path exists)
-
Inspect form submission data for injected scriptsIn WordPress admin, navigate to NEX-Forms > Submissions. Review recent form submissions and inspect the key names/values for any suspicious patterns such as <script> tags, javascript: URIs, onmouseover/onclick attributes, or encoded payloads.Affected if Form submissions contain unexpected HTML tags, script elements, or event handler attributes in parameter keys or values (potential exploitation indicator)
User is affected if NEX-Forms plugin version is 9.1.11 or lower AND forms are publicly accessible, particularly if suspicious script tags or event handlers are found in form submission data.
Generated from the published advisory. Verify against your own configuration.
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 · scopedImplement proper input sanitization for all POST parameter keys using whitelist validation or sanitization functions, and apply output escaping appropriate to context (htmlspecialchars for HTML content, esc_attr for attributes) before displaying any form submission data. Update to version 9.1.12 or later when available.
Latest version available on WordPress plugin repository (greater than 9.1.11)
- 1. Navigate to the WordPress admin dashboard
- 2. Go to Plugins > Installed Plugins
- 3. Locate the NEX-Forms plugin
- 4. Check the current installed version
- 5. If the installed version is 9.1.11 or lower, update to the latest available version from the WordPress plugin repository
- 6. Alternatively, download the latest version from plugins.trac.wordpress.org and upload manually
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5063 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5063 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