dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-41200

HIGH · 8.5 CVSS v4.0 Published 2026-04-23
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
Remotely reachable No privileges

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
STIG Manager is an API and web client for managing Security Technical Implementation Guides (STIG) assessments of Information Systems. Versions 1.5.10 through 1.6.7 have a reflected Cross-Site Scripting (XSS) vulnerability in the OIDC authentication error handling code in `src/init.js` and `public/reauth.html`. During the OIDC redirect flow, the `error` and `error_description` query parameters returned by the OIDC provider are written directly to the DOM via `innerHTML` without HTML escaping. An attacker who can craft a malicious redirect URL and convince a user to follow it can execute arbitrary JavaScript in the application's origin context. The vulnerability is most severe when the targeted user has an active STIG Manager session running in another browser tab — injected code executes in the same origin and can communicate with the SharedWorker managing the active access token, enabling authenticated API requests on behalf of the victim including reading and modifying collection data. The vulnerability is patched in version 1.6.8. There is no workaround short of upgrading. Deployments behind a web application firewall that filters reflected XSS payloads in query parameters may have partial mitigation, but this is not a substitute for patching.

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

STIG Manager versions 1.5.10-1.6.7 contain a reflected XSS vulnerability where OIDC authentication error parameters (error and error_description) are rendered directly to the DOM via innerHTML without HTML escaping. Attackers can craft malicious URLs that, when followed by authenticated users, execute arbitrary JavaScript in the victim's session context and interact with the SharedWorker to steal the access token for authenticated API calls.

MitigationUpgrade to version 1.6.8. A WAF may provide partial mitigation but is not a substitute for patching. No workaround exists short of upgrading.

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
Authentication
X
User interaction
A
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Identify installed STIG Manager version
    Check the application's version number in the UI (typically in the footer or About section) or check the container/package version if deployed via Docker or package manager
    Affected if Version is 1.5.10, 1.5.11, 1.5.12, 1.6.0, 1.6.1, 1.6.2, 1.6.3, 1.6.4, 1.6.5, 1.6.6, or 1.6.7 (any version from 1.5.10 through 1.6.7 inclusive)
  2. Confirm OIDC authentication is configured
    Review the STIG Manager configuration file (config.yaml or environment variables) for OIDC/OAuth2 provider settings such as clientId, issuer, authority, or similar OIDC-related parameters
    Affected if OIDC authentication is enabled and configured with an external identity provider
  3. Check if application serves login pages with error parameters
    Examine HTTP responses when accessing the login endpoint with crafted query parameters such as ?error=test or ?error_description=test to see if they are reflected unescaped in the HTML response
    Affected if The error or error_description parameter values appear in the response HTML without HTML entity encoding (e.g., < appears as < not &lt;)

You are affected if running STIG Manager version 1.5.10 through 1.6.7 with OIDC authentication enabled, and the OIDC error parameters are reflected unescaped in the login page.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 1.6.8. A WAF may provide partial mitigation but is not a substitute for patching. No workaround exists short of upgrading.

Recommended fix High confidence

1.6.8

  1. Download STIG Manager version 1.6.8 from the official GitHub repository (github.com/NuSecureDigital/STIG-Manager or the project releases page)
  2. Upgrade your STIG Manager installation to version 1.6.8 following the standard upgrade procedure for your deployment method (Docker, npm, or direct installation)
  3. Verify the upgrade was successful by checking the application version in the UI or via API
  4. Test the OIDC authentication flow to confirm the vulnerability is remediated - specifically verify that error and error_description query parameters are properly HTML-escaped when displayed

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-41200 — 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-2026-41200 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