How severe is CVE-2024-45119?

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

Which packages are affected by CVE-2024-45119?

CVE-2024-45119 affects the following packages: magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist), magento/community-edition (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2024-45119?

Update magento/community-edition to 2.4.7-p3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45119 is resolved across your whole dependency graph.

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

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

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

Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

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

No public exploit code has been indexed for CVE-2024-45119 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-45119?

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

CVE-2024-45119 is classified as Server-Side Request Forgery (SSRF) (CWE-918). 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-45119 published, and has it been updated?

CVE-2024-45119 was published on October 10, 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-45119 — community-edition

MEDIUM

CVE-2024-45119 is a medium-severity (CVSS 4.9) Server-Side Request Forgery (SSRF) vulnerability in magento/community-edition. A fix is available for magento/community-edition — see the affected versions and patch details below.

Adobe Commerce | Server-Side Request Forgery (SSRF) (CWE-918)

Also known asGHSA-g9fm-wc6h-pvgj

Published

Oct 10, 2024

Updated

Oct 28, 2026

Affected

8 pkgs

Patched

4 / 8

Exploits

None indexed

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

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

EPSS Exploitation Probability

via FIRST.org ↗

0.9%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs59th percentile — riskier than 59% 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

8 pkgs affected

🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition🐘magento/community-edition

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

Adobe Commerce versions 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 (and earlier) are affected by a Server-Side Request Forgery (SSRF) vulnerability that could lead to arbitrary file system read. An admin-privilege authenticated attacker can force the application to make arbitrary requests via injection of arbitrary URLs. Exploitation of this issue does not require user interaction.

Affected Packages

8 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`magento/community-edition`	≥ 2.4.7-beta1&&< 2.4.7-p3	2.4.7-p3`composer require magento/community-edition:^2.4.7-p3`
🐘Packagist	`magento/community-edition`	≥ 2.4.6-p1&&< 2.4.6-p8	2.4.6-p8`composer require magento/community-edition:^2.4.6-p8`
🐘Packagist	`magento/community-edition`	≥ 2.4.5-p1&&< 2.4.5-p10	2.4.5-p10`composer require magento/community-edition:^2.4.5-p10`
🐘Packagist	`magento/community-edition`	all versions	2.4.4-p11`composer require magento/community-edition:^2.4.4-p11`
🐘Packagist	`magento/community-edition`	all versions	No fix
🐘Packagist	`magento/community-edition`	all versions	No fix

Affected Products

3 products · 76 configurations

Application

commerceadobe

4 versions

2.4.42.4.52.4.62.4.7

Application

commerce b2badobe

4 versions

1.3.31.3.41.3.51.4.2

Application

magentoadobe

4 versions

2.4.42.4.52.4.62.4.7

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for magento/community-edition, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update magento/community-edition to 2.4.7-p3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-45119 is resolved across your whole dependency graph.
Workarounds
Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2024-45119 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

4.9/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

High

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-918Server-Side Request Forgery (SSRF)

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Oct 10, 2024

Last updated

Oct 28, 2026

Identifiers

CVE-2024-45119

GHSA-g9fm-wc6h-pvgj

References

Advisorygithub.com · CVE 2024 45119.json Advisoryhelpx.adobe.com · apsb24 73 Advisorynvd.nist.gov · CVE 2024 45119 Packagegithub.com · magento2

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting magento/community-edition are rated as high or higher (top: critical).

CVE-2025-54264CVE-2025-54263CVE-2025-54266CVE-2025-54267CVE-2025-54265CVE-2025-54236CVE-2025-49555CVE-2025-49556

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedOct 28, 2026

CVE-2024-45119 — community-edition

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2024-45119 in your dependencies?