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

CVE-2026-34416

MEDIUM · 6.1 CVSS v3.1 Published 2026-06-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
OSCAL-GUI contains a reflected cross-site scripting vulnerability that allows unauthenticated attackers to execute arbitrary JavaScript in a victim's browser by injecting malicious input through the project request parameter. Attackers can craft a malicious URL containing unsanitized input that breaks out of the JavaScript string and HTML attribute context in the body onload event handler to execute arbitrary scripts when the link is visited by a victim.

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

OSCAL-GUI has a reflected cross-site scripting vulnerability in the project request parameter. Unauthenticated attackers can inject malicious JavaScript through a crafted URL that breaks out of the JavaScript string and HTML attribute context in the body onload event handler, allowing arbitrary script execution in victim browsers.

MitigationImplement proper input validation and output encoding for the project parameter, ensuring all user-supplied input is sanitized before being rendered in HTML/JavaScript contexts, particularly within event handlers.

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

CVSS:3.1/AV:N/AC:L/PR:N/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. Identify OSCAL-GUI installation
    Locate the OSCAL-GUI application - this may be a web application, check for its web server, service, or installation directory. Look for files named osc-gui, oscal-gui, or related web application components.
    Affected if OSCAL-GUI is present in the environment and accessible as a web application
  2. Determine the web interface endpoint
    Identify the base URL where OSCAL-GUI serves its web interface. Check if it listens on common ports (80, 443, 8080) or review configuration files for the application URL.
    Affected if OSCAL-GUI is accessible via HTTP/HTTPS and responds to requests
  3. Locate the project parameter functionality
    Navigate to pages or endpoints that accept a 'project' request parameter. This is typically used when loading or managing OSCAL projects. Common URL patterns may include: /?project=NAME, /project/NAME, or similar.
    Affected if The application accepts a 'project' parameter in HTTP requests
  4. Verify parameter reflection in onload handler
    Send a test request with a benign value in the project parameter (e.g., project=test). Use browser dev tools or a proxy to examine the HTML response. Look for the project value inside a <body onload="..."> attribute.
    Affected if The project parameter value appears directly inside a body onload event handler without proper encoding or escaping
  5. Test for XSS injection
    Submit a crafted payload in the project parameter such as: ");alert(1);// This payload attempts to break out of the JavaScript string context in the onload handler. Examine the response to see if the payload is rendered as-is or if characters are escaped.
    Affected if Special characters like quotes and parentheses are not sanitized and can break out of the onload handler attribute context

A user is affected if OSCAL-GUI is running and the 'project' request parameter is reflected unescaped inside a body onload event handler, allowing injection of arbitrary JavaScript.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper input validation and output encoding for the project parameter, ensuring all user-supplied input is sanitized before being rendered in HTML/JavaScript contexts, particularly within event handlers.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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