NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
📦
📦 npm🐍 PyPI
Not in CISA KEV
MEDIUM severity

CVE-2024-21485 — dash-core-components

MEDIUMFix: plotly/dash@9920073

CVE-2024-21485 is a medium-severity (CVSS 6.5) Cross-site Scripting (XSS) vulnerability in dash-core-components. 6 public exploit or proof-of-concept references are indexed, 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

Also known asGHSA-547x-748v-vp6pPYSEC-2024-35PYSEC-2026-219PYSEC-2026-220
Published
Updated
Affected
5 pkgs
Patched
5 / 5
Exploits
6 known
Exploitation data as of Nov 4, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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 CVE-2024-21485.

EPSS Exploitation Probability

via FIRST.org ↗
1.5%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk
0.41%0.93%1.46%1.99%0.9%1.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

5 pkgs affected

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.

0other npm packages depend on this — each one inherits the vulnerability until it's patched upstream
dash-core-componentsnpm
4Kdownloads / week
dash-html-componentsnpm
1Kdownloads / week

Description

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

5 total 5 fixed
EcosystemPackageVulnerable rangeFix
📦npmdash-core-componentsall versions2.13.0npm install dash-core-components@2.13.0
📦npmdash-html-componentsall versions2.0.16npm install dash-html-components@2.0.16
🐍PyPIdash-html-componentsall versions2.0.0pip install --upgrade 'dash-html-components==2.0.0'
🐍PyPIdash-core-componentsall versions2.0.0pip install --upgrade 'dash-core-components==2.0.0'
🐍PyPIdashall versions2.15.0pip install --upgrade 'dash==2.15.0'

Affected Products

1 product · 2 configurations
Application
dashplotly
≥ 2.14.0 && < 2.15.0
range
Exploits & PoCs
6

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    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.

  2. 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 CVE-2024-21485 is resolved across your whole dependency graph.

  3. 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 CVE-2024-21485

A community-maintained Nuclei template exists for this CVE. You can scan for it directly:

nuclei -id cve-2024-21485 -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

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 al
O3 Security · Impact-Aware SCA

Is CVE-2024-21485 in your dependencies?

Find it across npm, PyPI, including transitive dependencies.

CVE-2024-21485: dash-core XSS — Fixed in 2.13.0