GHSA-547x-748v-vp6p is a medium-severity (CVSS 6.5) Cross-site Scripting (XSS) vulnerability in dash-core-components. 6 public exploit references exist, so weaponization risk is real. A fix is available for dash-core-components — see the affected versions and patch details below.
Dash apps vulnerable to Cross-site Scripting
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
Exploitation and automatability from CISA’s SSVC triage for GHSA-547x-748v-vp6p.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
GHSA-547x-748v-vp6p by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 379,842 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
dash-core-componentsnpmdash-html-componentsnpmDescription
Versions of the package dash-core-components before 2.13.0; versions of the package dash-core-components before 2.0.0; versions of the package dash before 2.15.0; versions of the package dash-html-components before 2.0.0; versions of the package dash-html-components before 2.0.16 are vulnerable to Cross-site Scripting (XSS) when the href of the a tag is controlled by an adversary. An authenticated attacker who stores a view that exploits this vulnerability could steal the data that's visible to another user who opens that view - not just the data already included on the page, but they could also, in theory, make additional requests and access other data accessible to this user. In some cases, they could also steal the access tokens of that user, which would allow the attacker to act as that user, including viewing other apps and resources hosted on the same server.
Note:
This is only exploitable in Dash apps that include some mechanism to store user input to be reloaded by a different user.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | dash-core-components | all versions | 2.13.0npm install dash-core-components@2.13.0 |
| 📦npm | dash-html-components | all versions | 2.0.16npm install dash-html-components@2.0.16 |
| 🐍PyPI | dash-html-components | all versions | 2.0.0pip install --upgrade 'dash-html-components==2.0.0' |
| 🐍PyPI | dash-core-components | all versions | 2.0.0pip install --upgrade 'dash-core-components==2.0.0' |
| 🐍PyPI | dash | all versions | 2.15.0pip install --upgrade 'dash==2.15.0' |
Affected Products
dashplotlyResearch use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Versions of the package dash-core-components before 2.13.0; versions of …
Versions of the package dash-core-components before 2.13.0; versions of …
Versions of the package dash-core-components before 2.13.0; versions of …
Versions of the package dash-core-components before 2.13.0; versions of …
Versions of the package dash-core-components before 2.13.0; versions of …
Versions of the package dash-core-components before 2.13.0; versions of …
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for dash-core-components, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update dash-core-components to 2.13.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-547x-748v-vp6p is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
How to detect GHSA-547x-748v-vp6p
A community-maintained Nuclei template exists for this CVE. You can scan for it directly:
nuclei -id ghsa-547x-748v-vp6p -u https://target- Template
- Dash Framework - Cross-site Scripting
- Severity
- medium
- Impact
- Data theft from users who access the compromised view and Access token stealing allowing attacker to impersonate users
- Remediation
- Upgrade to dash version 2.15.0 or later
Template by ProjectDiscovery nuclei-templates (Lee Changhyun(eeche)), MIT licensed. View the full template. Scan only systems you are authorised to test.
Frequently Asked Questions
Is GHSA-547x-748v-vp6p in your dependencies?
Find it across npm, PyPI, including transitive dependencies.