CVE-2024-37296 is a medium-severity (CVSS 5.3) CWE-841 vulnerability in aimeos/ai-client-html. A fix is available for aimeos/ai-client-html — see the affected versions and patch details below.
Aimeos HTML client vulnerable to digital products download without proper payment status check
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2024-37296.
EPSS Exploitation Probability
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-37296 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 377,166 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
aimeos/ai-client-html🐘aimeos/ai-client-html🐘aimeos/ai-client-html🐘aimeos/ai-client-html🐘aimeos/ai-client-htmlReal-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
The Aimeos HTML client provides Aimeos HTML components for e-commerce projects. Starting in version 2020.04.1 and prior to versions 2020.10.27, 2021.10.21, 2022.10.12, 2023.10.14, and 2024.04.5, digital downloads sold in online shops can be downloaded without valid payment, e.g. if the payment didn't succeed. Versions 2020.10.27, 2021.10.21, 2022.10.12, 2023.10.14, and 2024.04.5 fix this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | aimeos/ai-client-html | ≥ 2024.04.1&&< 2024.04.5 | 2024.04.5composer require aimeos/ai-client-html:^2024.04.5 |
| 🐘Packagist | aimeos/ai-client-html | ≥ 2023.04.1&&< 2023.10.14 | 2023.10.14composer require aimeos/ai-client-html:^2023.10.14 |
| 🐘Packagist | aimeos/ai-client-html | ≥ 2022.04.1&&< 2022.10.12 | 2022.10.12composer require aimeos/ai-client-html:^2022.10.12 |
| 🐘Packagist | aimeos/ai-client-html | ≥ 2021.04.1&&< 2021.10.21 | 2021.10.21composer require aimeos/ai-client-html:^2021.10.21 |
| 🐘Packagist | aimeos/ai-client-html | ≥ 2020.04.1&&< 2020.10.27 | 2020.10.27composer require aimeos/ai-client-html:^2020.10.27 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aimeos/ai-client-html, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aimeos/ai-client-html to 2024.04.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-37296 is resolved across your whole dependency graph.
Workarounds
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 O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2024-37296 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-37296. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-37296 in your dependencies?
O3 Security finds CVE-2024-37296 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.