Summary
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.
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.
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.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2025-64758 has a CVSS score of 4.8 (Medium). The vector is network-reachable, high privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.13.6); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
The issue has been fixed in version 4.13.6.
Frequently Asked Questions
- What is CVE-2025-64758? CVE-2025-64758 is a medium-severity cross-site scripting (XSS) vulnerability in @dependencytrack/frontend (npm), affecting versions >= 4.12.0, < 4.13.6. It is fixed in 4.13.6. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is CVE-2025-64758? CVE-2025-64758 has a CVSS score of 4.8 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of @dependencytrack/frontend are affected by CVE-2025-64758? @dependencytrack/frontend (npm) versions >= 4.12.0, < 4.13.6 is affected.
- Is there a fix for CVE-2025-64758? Yes. CVE-2025-64758 is fixed in 4.13.6. Upgrade to this version or later.
- Is CVE-2025-64758 exploitable, and should I be worried? Whether CVE-2025-64758 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2025-64758 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2025-64758? Upgrade
@dependencytrack/frontendto 4.13.6 or later.