CVE-2026-8474
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 · uneditedA vulnerability was discovered on Stormshield Network Security * 4.3.0 to 4.3.41, * 4.8.0 to 4.8.15, * 5.0.0 to 5.0.5 It is possible to execute a reflected XSS attack on the login API available on Stormshield SNS appliance by executing a script on the victim's machine. The risks include the theft of cookies or other sensitive data, as well as the modification of page behavior, for example, by redirecting the victim to malicious websites.
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 confidenceA reflected XSS vulnerability exists in the login API of Stormshield SNS appliances across versions 4.3.0-4.3.41, 4.8.0-4.8.15, and 5.0.0-5.0.5. Attackers can inject malicious scripts that execute in victims' browsers, enabling cookie theft, sensitive data exfiltration, and page behavior modification including redirect attacks.
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
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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.
-
Confirm Stormshield SNS is installedIdentify whether Stormshield SNS appliance software is running in your environment. This may be visible in network scans, device inventory, or system documentation.Affected if Stormshield SNS software is present in your environment
-
Determine the installed SNS versionAccess the appliance administrative interface or use the CLI command 'nsml show version' or check the system information page in the web management console to retrieve the exact version number.Affected if The installed version falls within 4.3.0-4.3.41, 4.8.0-4.8.15, or 5.0.0-5.0.5
-
Verify the login API endpoint is accessibleCheck if the login API endpoint is exposed externally or internally by attempting to access the login page URL (typically /cgi-bin/nxadm.cgi or /auth/login) on the appliance. Review firewall or proxy logs for access attempts to these paths.Affected if The login API endpoint is reachable from any network where potential attackers could send malicious requests
-
Inspect login request parameters for sanitizationIf you have access to logs or can test safely, examine whether the login API properly encodes or sanitizes input parameters. Submit a test XSS payload in the username or other login fields and check if it is reflected unescaped in the response.Affected if Login input parameters are reflected in responses without HTML encoding or sanitization
Your environment is affected if Stormshield SNS is running and the installed version falls within 4.3.0-4.3.41, 4.8.0-4.8.15, or 5.0.0-5.0.5, and the login API endpoint is accessible to potential attackers.
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 dataApply vendor-supplied patches or upgrade to a patched Stormshield SNS version beyond 5.0.5. Validate the login API response encoding and implement Content Security Policy headers as a defense-in-depth measure.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-8474 — 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-8474 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