CVE-2026-2440
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 SurveyJS plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to, and including, 2.5.3 via survey result submissions. This is due to insufficient input sanitization and output escaping. The public survey page exposes the nonce required for submission, allowing unauthenticated attackers to submit HTML-encoded payloads that are decoded and rendered as executable HTML when an administrator views survey results, leading to stored XSS in the admin context.
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 SurveyJS WordPress plugin (versions up to 2.5.3) suffers from a stored XSS vulnerability in survey result submissions. Unauthenticated attackers can submit HTML-encoded malicious payloads via the public survey form (which exposes the submission nonce). These payloads are stored and executed when an administrator views the survey results in the admin dashboard, as the plugin fails to properly sanitize input and escape output.
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.
-
Check SurveyJS plugin versionIn WordPress admin, go to Plugins > Installed Plugins > SurveyJS and look at the Version number. Alternatively, check the plugin files in /wp-content/plugins/surveyjs/ for a version file or header comment.Affected if The installed version is 2.5.3 or any earlier version (e.g., 2.5.2, 2.5.1, 2.0.0, etc.)
-
Identify exposed survey formsLook for publicly accessible survey URLs on your site. Check if the survey form endpoint is reachable without authentication - typically URLs containing /surveyjs/ or similar patterns are publicly available.Affected if Public survey forms are enabled and accessible to unauthenticated users, exposing the submission nonce
-
Review survey result submissionsIn WordPress admin, navigate to the SurveyJS results or submissions view. Inspect the stored survey responses for any unexpected HTML, script tags, or encoded payloads in text fields.Affected if Survey submissions contain unsanitized HTML or script tags that could execute when viewed in the admin dashboard
-
Verify admin result viewing pageAccess the survey results page in the WordPress admin dashboard (typically under SurveyJS menu). Observe whether the page renders submitted data without proper escaping.Affected if The admin can view survey results and the output is not sanitized/escaped when displaying submitted values
You are affected if the SurveyJS plugin version is 2.5.3 or earlier AND public survey forms are enabled, allowing unauthenticated submissions that can contain malicious scripts stored in the database.
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.
From vendor dataUpdate the SurveyJS plugin to a version beyond 2.5.3 when available; alternatively, restrict access to the survey results admin page until the patch is applied.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2440 — 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-2440 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