How severe is CVE-2024-21517?

No CVSS score has been assigned to CVE-2024-21517 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2024-21517?

CVE-2024-21517 affects the following packages: opencart/opencart (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2024-21517?

No patched version of opencart/opencart has shipped for CVE-2024-21517 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

How do I detect CVE-2024-21517 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for opencart/opencart, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

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

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.

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

Yes. There are 1 known exploit references for CVE-2024-21517, including 1 in-the-wild exploitation 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-21517?

CVE-2024-21517 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 31th 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-21517?

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

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

CVE-2024-21517 was published on June 22, 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.

🐘 Packagist

Not in CISA KEV

CVE-2024-21517 — opencart/opencart

Fix: opencart/opencart@0fd1ee4

CVE-2024-21517 is a Cross-site Scripting (XSS) vulnerability in opencart/opencart. 1 public exploit reference exists, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

Cross site scripting in opencart

Also known asBIT-opencart-2024-21517GHSA-qc3q-8rr8-8p5v

Published

Jun 22, 2024

Updated

Aug 12, 2026

Affected

1 pkg

Patched

See advisory

Exploits

1 known

Exploitation data as of Sep 26, 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-21517.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs31th percentile — riskier than 31% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

🐘opencart/opencart

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

This affects versions of the package opencart/opencart from 4.0.0.0. A reflected XSS issue was identified in the redirect parameter of customer account/login route. An attacker can inject arbitrary HTML and Javascript into the page response. As this vulnerability is present in the account functionality it could be used to target and attack customers of the OpenCart shop.

Notes:

The fix for this vulnerability is incomplete

Affected Packages

1 total

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`opencart/opencart`	≥ 4.0.0.0	No fix

Affected Products

1 product · 1 configurations

Application

opencartopencart

≥ 4.0.0.0

range

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.

This affects versions of the package opencart/opencart from 4.0.0.0. A r…

security.snyk.ioNVDJun 2024

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for opencart/opencart, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Remediation status
No patched version of opencart/opencart has shipped for CVE-2024-21517 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
Mitigate without a patch
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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-21517 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works