CVE 8.5 HIGH

STIG Manager has reflected XSS vulnerability in the Web App_CVE-2026-41200

8.5 / 10
HIGH
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

Description

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.

AI Analysis

Reflected Cross-Site Scripting (XSS) vulnerability in the OIDC authentication error handling code

Basic Information

ID CVE-2026-41200
Source GitHub_M
Published Apr 23, 2026 at 00:40

Affected Product

Vendor NUWCDIVNPT
Product stig-manager
Version >= 1.5.10, < 1.6.8
Affected Versions NUWCDIVNPT stig-manager >= 1.5.10, < 1.6.8

CWE Classification

AI Assessment

AI Score 8.5 / 10
AI Severity High
Vendor NUWCDIVNPT
Product STIG Manager
Version 1.5.10-1.6.7

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.