How severe is CVE-2024-21485?

CVE-2024-21485 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2024-21485?

CVE-2024-21485 affects the following packages: dash-core-components (npm), dash-html-components (npm), dash-html-components (PyPI), dash-core-components (PyPI), dash (PyPI). Ecosystems affected: npm, PyPI.

How do I fix CVE-2024-21485?

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.

How do I detect CVE-2024-21485 in my npm, PyPI dependencies?

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.

How do I mitigate CVE-2024-21485 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2024-21485?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-21485 can be triaged on real exposure rather than presence alone.

Is CVE-2024-21485 actively exploited in the wild?

Yes. There are 6 known exploit references for CVE-2024-21485, including 6 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2024-21485?

CVE-2024-21485 has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 73th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2024-21485?

CVE-2024-21485 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2024-21485?

A Nuclei detection template exists for CVE-2024-21485, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2024-21485 published, and has it been updated?

CVE-2024-21485 was published on February 2, 2024 and was last updated on August 12, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 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 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

Also known asGHSA-547x-748v-vp6pPYSEC-2024-35PYSEC-2026-219PYSEC-2026-220

Published

Feb 2, 2024

Updated

Aug 12, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

6 known

Exploitation data as of Sep 23, 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 CVEs73th percentile — riskier than 73% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

How urgent is this, really

CVE-2024-21485 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.

Where this sits among everything scored

Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.

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

3Kdownloads / 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

Ecosystem	Package	Vulnerable range	Fix
📦npm	`dash-core-components`	all versions	2.13.0`npm install dash-core-components@2.13.0`
📦npm	`dash-html-components`	all versions	2.0.16`npm install dash-html-components@2.0.16`
🐍PyPI	`dash-html-components`	all versions	2.0.0`pip install --upgrade 'dash-html-components==2.0.0'`
🐍PyPI	`dash-core-components`	all versions	2.0.0`pip install --upgrade 'dash-core-components==2.0.0'`
🐍PyPI	`dash`	all versions	2.15.0`pip install --upgrade 'dash==2.15.0'`

Exploits & PoCs

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