GHSA-7xvh-c266-cfr5
MEDIUMGHSA-7xvh-c266-cfr5 is a medium-severity (CVSS 4.8) Cross-site Scripting (XSS) vulnerability in @dependencytrack/frontend. O3 Security confirms whether GHSA-7xvh-c266-cfr5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
@dependencytrack/frontend vulnerable to Persistent Cross-Site-Scripting via welcome message
Blast Radius
Weekly download volume for affected packages — a proxy for how broadly this vulnerability is deployed.
@dependencytrack/frontendnpmDescription
Description
Since version 4.12.0, Dependency-Track users with the SYSTEM_CONFIGURATION permission can configure a "welcome message", which is HTML that is to be rendered on the login page for branding purposes.
When rendering the welcome message, Dependency-Track versions before 4.13.6 did not properly sanitize the HTML, allowing arbitrary JavaScript to be executed.
Impact
Users with the SYSTEM_CONFIGURATION permission (i.e., administrators), can exploit this weakness to execute arbitrary JavaScript for users browsing to the login page.
Patches
The issue has been fixed in version 4.13.6.
References
- The issue was introduced via: https://github.com/DependencyTrack/frontend/pull/986
- The issue was fixed via: https://github.com/DependencyTrack/frontend/pull/1378
Credit
Thanks to Jonas Benjamin Friedli for identifying and responsibly disclosing the issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @dependencytrack/frontend | ≥ 4.12.0&&< 4.13.6 | 4.13.6 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @dependencytrack/frontend. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @dependencytrack/frontend to 4.13.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7xvh-c266-cfr5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-7xvh-c266-cfr5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-7xvh-c266-cfr5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-7xvh-c266-cfr5 in your dependencies?
O3 detects GHSA-7xvh-c266-cfr5 across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.