How severe is CVE-2024-39319?

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

Which packages are affected by CVE-2024-39319?

CVE-2024-39319 affects the following packages: aimeos/ai-controller-frontend (Packagist), aimeos/ai-controller-frontend (Packagist), aimeos/ai-controller-frontend (Packagist), aimeos/ai-controller-frontend (Packagist), aimeos/ai-controller-frontend (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2024-39319?

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.

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

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.

How do I mitigate CVE-2024-39319 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.

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

No public exploit code has been indexed for CVE-2024-39319 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

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

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

CVE-2024-39319 is classified as CWE-639 (CWE-639). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2024-39319 was published on September 26, 2024 and was last updated on October 28, 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

MEDIUM severity

CVE-2024-39319 — ai-controller-frontend

MEDIUMFix: aimeos/ai-controller-frontend@2ad5c06

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

Also known asGHSA-rw3j-574h-mrcq

Published

Sep 26, 2024

Updated

Oct 28, 2026

Affected

5 pkgs

Patched

5 / 5

Exploits

None indexed

Exploitation data as of Nov 1, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs42th percentile — riskier than 42% of all scored CVEsHighest risk

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

🐘aimeos/ai-controller-frontend🐘aimeos/ai-controller-frontend🐘aimeos/ai-controller-frontend🐘aimeos/ai-controller-frontend🐘aimeos/ai-controller-frontend

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

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

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`aimeos/ai-controller-frontend`	≥ 2024.04.1&&< 2024.04.2	2024.04.2`composer require aimeos/ai-controller-frontend:^2024.04.2`
🐘Packagist	`aimeos/ai-controller-frontend`	≥ 2023.04.1&&< 2023.10.9	2023.10.9`composer require aimeos/ai-controller-frontend:^2023.10.9`
🐘Packagist	`aimeos/ai-controller-frontend`	≥ 2022.04.1&&< 2022.10.8	2022.10.8`composer require aimeos/ai-controller-frontend:^2022.10.8`
🐘Packagist	`aimeos/ai-controller-frontend`	≥ 2021.04.1&&< 2021.10.8	2021.10.8`composer require aimeos/ai-controller-frontend:^2021.10.8`
🐘Packagist	`aimeos/ai-controller-frontend`	all versions	2020.10.15`composer require aimeos/ai-controller-frontend:^2020.10.15`

Affected Products

1 product · 5 configurations

Application

aimeos frontend controlleraimeos

≥ 2023.04.1 && < 2023.10.9

1 version

2024.04.1

Detection & mitigation playbook

Open-source dependency

Detect
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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-39319 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works