dbcve.org
NgsurveyApplication

CVE-2025-15479

MEDIUM · 5.4 CVSS v3.1 Published 2026-01-07
Fix available
A fix is available. Upgrade to 3.6.17 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
Stored cross-site scripting (XSS, CWE-79) in the survey content and administration functionality in Data Illusion Zumbrunn NGSurvey Enterprise Edition 3.6.4 on all supported platforms ( on Windows and Linux servers ) allows authenticated remote users with survey creation or edit privileges to execute arbitrary JavaScript in other users’ browsers, steal session information and perform unauthorized actions on their behalf via crafted survey content that is rendered without proper output encoding.

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 confidence

Stored XSS vulnerability in Data Illusion NGSurvey Enterprise Edition 3.6.4 allows authenticated users with survey creation/edit privileges to inject malicious JavaScript into survey content. When other users view the survey, the injected script executes without proper output encoding, enabling session theft and unauthorized actions.

MitigationImplement proper output encoding/escaping on all survey content rendered in user browsers. Input validation should also be added server-side. Review and sanitize existing survey content in the database for malicious payloads.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
NgsurveyApplication
Affected:< 3.6.17

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 checks

Work through these to decide whether this CVE applies to you.

  1. Determine installed NGSurvey version
    Locate the NGSurvey version information in the application admin panel, about page, or check the software installation metadata. Common locations include the control panel, system info, or version file in the application root.
    Affected if The installed version is lower than 3.6.17 (e.g., 3.6.4 or any version < 3.6.17)
  2. Identify users with survey creation or edit privileges
    Review the NGSurvey user role configuration and permission settings. Check the user management section to list accounts assigned roles that include survey creation or editing capabilities.
    Affected if Any user account has survey creation or survey edit permissions enabled in the system
  3. Inspect existing survey content for injected scripts
    Access the database or survey management interface to view stored survey questions, answers, and content fields. Look for script tags, event handlers (onclick, onerror, etc.), or encoded JavaScript payloads within survey text fields.
    Affected if Any survey contains unsanitized HTML or JavaScript code in title, question, or response fields that was not intentionally authored
  4. Verify output encoding on survey rendering
    Create a test survey with a benign payload such as <script>alert(1)</script> in a survey field, then view that survey as a different user. Examine the page source to see if the payload is rendered as raw text or executed as code.
    Affected if The test payload executes as JavaScript (triggers an alert or similar) when viewing the survey, indicating missing output encoding

You are affected if your NGSurvey version is below 3.6.17 and surveys can render user-submitted content without sanitization, allowing stored XSS to execute in other users browsers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.6.17 or later
Fixed in 3.6.17
Interim mitigation

Implement proper output encoding/escaping on all survey content rendered in user browsers. Input validation should also be added server-side. Review and sanitize existing survey content in the database for malicious payloads.

Recommended fix High confidence

Ngsurvey 3.6.17

  1. Backup the existing Ngsurvey installation and database before proceeding with any changes.
  2. Download Ngsurvey version 3.6.17 or later from the official vendor distribution source (docs.ngsurvey.com or the Thales Group CDS portal).
  3. Follow the standard Ngsurvey upgrade procedure documented in the administration guide for your platform (Windows or Linux).
  4. After upgrade, verify that survey content with special characters is properly encoded when rendered.
  5. Test that authenticated users with survey creation/edit privileges can create and save surveys without the XSS payload executing in other users' sessions.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Ngsurvey Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15479 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15479 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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