@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. Due to the common practice of providing vulnerability details in markdown format, the Dependency-Track frontend renders them using the JavaScript library Showdown. Showdown does not have any XSS countermeasures built in, and versions before 4.6.1 of the Dependency-Track frontend did not encode or sanitize Showdown's output. This made it possible for arbitrary JavaScript included in vulnerability details via HTML attributes to be executed in context of the frontend. Actors with the VULNERABILITY_MANAGEMENT permission can exploit this weakness by creating or editing a custom vulnerability and providing XSS payloads in any of the following fields: Description, Details, Recommendation, or References. The payload will be executed for users with the VIEW_PORTFOLIO permission when browsing to the modified vulnerability's page. Alternatively, malicious JavaScript could be introduced via any of the vulnerability databases mirrored by Dependency-Track. However, this attack vector is highly unlikely, and the maintainers of Dependency-Track are not aware of any occurrence of this happening. Note that the Vulnerability Details element of the Audit Vulnerabilities tab in the project view is not affected. The issue has been fixed in frontend version 4.6.1.
CVE-2022-39350
This medium-severity CVE scores 5.4 under NVD CVSS v3. EPSS exploit probability: 0.7% (52nd percentile of EPSS-scored CVEs). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
- Lower severity and no public exploit yet
A fix is available — apply it.
- CVSS v3
- 5.4
- EG Score
- 5.4MEDIUMmedium confidence
- EG Risk
- 25EG Risk 25/100CISA SSVC
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity54% × 45%Exploitation1% × 40%Automatability0% × 15%CISA SSVC: Track at every mission impact level.Action: A fix is available. Apply it within your standard update timelines. - EPSS PROB
- 0.7%
- EPSS %ILE
- 53rd
- KEV
- Not listed
CISA SSVCTrack at every mission impact level.
A fix is available. Apply it within your standard update timelines.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table
Published
October 25, 2022
Last Modified
November 21, 2024
References (6)
- security-advisories@githubhttps://docs.dependencytrack.org/changelog/
- security-advisories@githubhttps://github.com/DependencyTrack/frontend/security/advisories/GHSA-c33w-pm52-mqvf
- security-advisories@githubhttps://github.com/showdownjs/showdown/wiki/Markdown%27s-XSS-Vulnerability-%28and-how-to-mitigate-it%29
- af854a3a-2127-422b-91ae-364da2661108https://docs.dependencytrack.org/changelog/
- af854a3a-2127-422b-91ae-364da2661108https://github.com/DependencyTrack/frontend/security/advisories/GHSA-c33w-pm52-mqvf
- af854a3a-2127-422b-91ae-364da2661108https://github.com/showdownjs/showdown/wiki/Markdown%27s-XSS-Vulnerability-%28and-how-to-mitigate-it%29
Affected Packages
(1 across 1 ecosystem)
npm(1)
| Package | Vulnerable range | Fix by version range | Dependents |
|---|---|---|---|
| @dependencytrack/frontend | — |
| — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 7× in last 7d / 27× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
Showing the most recent 100 of 189 total refreshes for this CVE.
- 2026-10-10 19:56 UTCEPSS rescore
- 2026-10-09 20:04 UTCEPSS rescore
- 2026-10-08 16:40 UTCEPSS rescore
- 2026-10-07 23:45 UTCEPSS rescore
- 2026-10-06 15:14 UTCEPSS rescore
- 2026-10-05 17:40 UTCEPSS rescore
- 2026-10-04 23:19 UTCEPSS rescore
- 2026-10-03 14:23 UTCEPSS rescore
- 2026-10-02 16:23 UTCEPSS rescore
- 2026-10-01 19:47 UTCEPSS rescore
- 2026-09-30 16:03 UTCEG score recompute
- 2026-09-30 15:00 UTCEPSS rescore
- 2026-09-29 15:16 UTCEPSS rescore
- 2026-09-27 13:42 UTCEPSS rescore
- 2026-09-26 00:22 UTCEPSS rescore
- 2026-09-24 14:00 UTCEPSS rescore
- 2026-09-24 07:18 UTCOSV refresh
- 2026-09-22 14:45 UTCEPSS rescore
- 2026-09-20 20:13 UTCEPSS rescore
- 2026-09-20 20:13 UTCEPSS rescore
- 2026-09-19 15:38 UTCEPSS rescore
- 2026-09-17 19:24 UTCEPSS rescore
- 2026-09-16 14:05 UTCEPSS rescore
- 2026-09-15 03:07 UTCEPSS rescore
- 2026-09-12 14:57 UTCEPSS rescore
Show 75 moreShow fewer
- 2026-09-11 14:50 UTCEPSS rescore
- 2026-09-11 09:33 UTCEPSS rescore
- 2026-09-08 21:57 UTCEPSS rescore
- 2026-09-07 15:58 UTCEPSS rescore
- 2026-09-06 13:45 UTCEPSS rescore
- 2026-09-05 15:25 UTCEPSS rescore
- 2026-09-05 00:44 UTCOSV refresh
- 2026-09-04 13:57 UTCEPSS rescore
- 2026-09-04 05:04 UTCEPSS rescore
- 2026-09-02 14:09 UTCEPSS rescore
- 2026-09-01 13:51 UTCEPSS rescore
- 2026-08-30 19:14 UTCEPSS rescore
- 2026-08-30 01:19 UTCEPSS rescore
- 2026-08-28 21:38 UTCEPSS rescore
- 2026-08-27 14:22 UTCEPSS rescore
- 2026-08-26 14:43 UTCEPSS rescore
- 2026-08-25 13:46 UTCEPSS rescore
- 2026-08-24 14:13 UTCEPSS rescore
- 2026-08-23 00:17 UTCEPSS rescore
- 2026-08-21 23:46 UTCEPSS rescore
- 2026-08-21 23:46 UTCEPSS rescore
- 2026-08-20 22:52 UTCEPSS rescore
- 2026-08-19 17:01 UTCEPSS rescore
- 2026-08-18 13:45 UTCEPSS rescore
- 2026-08-18 11:32 UTCOSV refresh
- 2026-08-17 13:44 UTCEPSS rescore
- 2026-08-16 14:53 UTCEPSS rescore
- 2026-08-16 02:11 UTCEPSS rescore
- 2026-08-15 01:27 UTCEPSS rescore
- 2026-08-13 21:58 UTCEPSS rescore
- 2026-08-13 21:58 UTCEPSS rescore
- 2026-08-12 13:48 UTCEPSS rescore
- 2026-08-11 13:39 UTCEPSS rescore
- 2026-08-10 14:08 UTCEPSS rescore
- 2026-08-09 13:44 UTCEPSS rescore
- 2026-08-08 16:34 UTCEPSS rescore
- 2026-08-07 16:24 UTCEPSS rescore
- 2026-08-06 13:44 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-08-05 19:15 UTCEPSS rescore
- 2026-08-04 15:07 UTCEPSS rescore
- 2026-08-04 10:35 UTCEPSS rescore
- 2026-08-03 07:27 UTCOSV refresh
- 2026-08-02 02:24 UTCEPSS rescore
- 2026-08-01 04:13 UTCEPSS rescore
- 2026-07-30 16:25 UTCEPSS rescore
- 2026-07-30 16:25 UTCEPSS rescore
- 2026-07-30 01:28 UTCEPSS rescore
- 2026-07-28 15:33 UTCEPSS rescore
- 2026-07-26 14:52 UTCEPSS rescore
- 2026-07-25 14:15 UTCEPSS rescore
- 2026-07-25 14:15 UTCEPSS rescore
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-24 14:15 UTCEPSS rescore
- 2026-07-23 14:16 UTCEPSS rescore
- 2026-07-23 02:13 UTCEG score recompute
- 2026-07-22 23:00 UTCEG score recompute
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-22 14:06 UTCEPSS rescore
- 2026-07-21 15:23 UTCEPSS rescore
- 2026-07-21 15:22 UTCEPSS rescore
- 2026-07-20 17:05 UTCEPSS rescore
- 2026-07-19 14:29 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-19 02:27 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-18 10:03 UTCEPSS rescore
- 2026-07-16 17:00 UTCEPSS rescore
- 2026-07-16 16:53 UTCOSV refresh
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 16:56 UTCEPSS rescore
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-15 01:58 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
- 2026-07-13 22:28 UTCEPSS rescore
Related CVEs(same product + same CWE)
Frequently asked(5)
What is CVE-2022-39350?
When was CVE-2022-39350 disclosed?
Is CVE-2022-39350 actively exploited?
What is the CVSS score of CVE-2022-39350?
How do I remediate CVE-2022-39350?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2022-39350
Is Your Infrastructure Affected by CVE-2022-39350?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.