FKIE_CVE-2025-64758
Vulnerability from fkie_nvd - Published: 2025-11-17 18:15 - Updated: 2026-10-18 20:10| Vendor | Product | Version |
|---|
{
"affected": [
{
"affectedData": [
{
"product": "frontend",
"vendor": "DependencyTrack",
"versions": [
{
"status": "affected",
"version": "\u003e= 4.12.0, \u003c 4.13.6"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "@dependencytrack/frontend is a Single Page Application (SPA) used in Dependency-Track, an open source Component Analysis platform that allows organizations to identify and reduce risk in the software supply chain. 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. Users with the SYSTEM_CONFIGURATION permission (i.e., administrators), can exploit this weakness to execute arbitrary JavaScript for users browsing to the login page. The issue has been fixed in version 4.13.6."
},
{
"lang": "es",
"value": "@dependencytrack/frontend es una Aplicaci\u00f3n de P\u00e1gina \u00danica (SPA) utilizada en Dependency-Track, una plataforma de An\u00e1lisis de Componentes de c\u00f3digo abierto que permite a las organizaciones identificar y reducir el riesgo en la cadena de suministro de software. Desde la versi\u00f3n 4.12.0, los usuarios de Dependency-Track con el permiso SYSTEM_CONFIGURATION pueden configurar un \u201cmensaje de bienvenida\u201d, que es HTML que se renderizar\u00e1 en la p\u00e1gina de inicio de sesi\u00f3n con fines de marca. Al renderizar el mensaje de bienvenida, las versiones de Dependency-Track anteriores a la 4.13.6 no sanitizaban correctamente el HTML, permitiendo la ejecuci\u00f3n de JavaScript arbitrario. Los usuarios con el permiso SYSTEM_CONFIGURATION (es decir, administradores) pueden exploit esta vulnerabilidad para ejecutar JavaScript arbitrario para los usuarios que navegan a la p\u00e1gina de inicio de sesi\u00f3n. El problema ha sido solucionado en la versi\u00f3n 4.13.6."
}
],
"id": "CVE-2025-64758",
"lastModified": "2026-10-18T20:10:00.110",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 4.8,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "HIGH",
"scope": "CHANGED",
"userInteraction": "REQUIRED",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 1.7,
"impactScore": 2.7,
"source": "security-advisories@github.com",
"type": "Secondary"
}
],
"ssvcV203": [
{
"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0",
"ssvcData": {
"id": "CVE-2025-64758",
"options": [
{
"exploitation": "none"
},
{
"automatable": "no"
},
{
"technicalImpact": "partial"
}
],
"role": "CISA Coordinator",
"timestamp": "2025-11-17T21:05:00.585584Z",
"version": "2.0.3"
}
}
]
},
"published": "2025-11-17T18:15:58.450",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/DependencyTrack/frontend/commit/8fd757be612eaf4f35eadbe4c334204d7bd711be"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/DependencyTrack/frontend/pull/1378"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/DependencyTrack/frontend/pull/986"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/DependencyTrack/frontend/security/advisories/GHSA-7xvh-c266-cfr5"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-79"
}
],
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.