CVE-2024-39319 is a medium-severity (CVSS 5.3) CWE-639 vulnerability in aimeos/ai-controller-frontend. A fix is available for aimeos/ai-controller-frontend — see the affected versions and patch details below.
aimeos/ai-controller-frontend has IDOR vulnerability in account profile page
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-39319 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 376,715 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-controller-frontend🐘aimeos/ai-controller-frontend🐘aimeos/ai-controller-frontend🐘aimeos/ai-controller-frontend🐘aimeos/ai-controller-frontendReal-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
aimeos/ai-controller-frontend is the Aimeos frontend controller package for e-commerce projects. Prior to versions 2024.4.2, 2023.10.9, 2022.10.8, 2021.10.8, and 2020.10.15, an insecure direct object reference allows an attacker to disable subscriptions and reviews of another customer. Versions 2024.4.2, 2023.10.9, 2022.10.8, 2021.10.8, and 2020.10.15 fix this issue.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | aimeos/ai-controller-frontend | ≥ 2024.04.1&&< 2024.04.2 | 2024.04.2composer require aimeos/ai-controller-frontend:^2024.04.2 |
| 🐘Packagist | aimeos/ai-controller-frontend | ≥ 2023.04.1&&< 2023.10.9 | 2023.10.9composer require aimeos/ai-controller-frontend:^2023.10.9 |
| 🐘Packagist | aimeos/ai-controller-frontend | ≥ 2022.04.1&&< 2022.10.8 | 2022.10.8composer require aimeos/ai-controller-frontend:^2022.10.8 |
| 🐘Packagist | aimeos/ai-controller-frontend | ≥ 2021.04.1&&< 2021.10.8 | 2021.10.8composer require aimeos/ai-controller-frontend:^2021.10.8 |
| 🐘Packagist | aimeos/ai-controller-frontend | all versions | 2020.10.15composer require aimeos/ai-controller-frontend:^2020.10.15 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for aimeos/ai-controller-frontend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update aimeos/ai-controller-frontend to 2024.04.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-39319 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-39319 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2024-39319. 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-39319 in your dependencies?
O3 Security finds CVE-2024-39319 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.