CVE-2024-45119: Magento Community Edition SSRF Vulnerability Leading to Arbitrary File Access

magento/community-edition Updated 02 Oct 2025

Summary

10/10/2024
Yes i
Moderate
4.9

CVE-2024-45119: Magento Open Source Server-Side Request Forgery (SSRF) vulnerability. Affects magento/community-edition across 4 version ranges.

< 2.4.4-p11 >= 2.4.5-p1, < 2.4.5-p10 >= 2.4.6-p1, < 2.4.6-p8 >= 2.4.7-beta1, < 2.4.7-p3

Fixed in 4 releases; the minimum fixed version depends on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Magento is a widely-used open-source e-commerce platform that provides a flexible and scalable solution for online businesses. It offers a range of features including product management, customer management, and order processing. However, certain versions of Magento are vulnerable to a Server-Side Request Forgery (SSRF) vulnerability, which can compromise the security of the application.

Vulnerability Detail

The SSRF vulnerability in Adobe Commerce versions 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier allows low-privilege authenticated attackers to manipulate the application into making arbitrary requests. This can lead to unauthorized access to sensitive files on the server, impacting both confidentiality and integrity. The vulnerability arises from improper validation of user-supplied URLs, enabling attackers to exploit the application without user interaction.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 2.4.4-p11 2.4.4-p11
    composer require magento/community-edition:2.4.4-p11
  • >= 2.4.5-p1, < 2.4.5-p10 2.4.5-p10
    composer require magento/community-edition:2.4.5-p10
  • >= 2.4.6-p1, < 2.4.6-p8 2.4.6-p8
    composer require magento/community-edition:2.4.6-p8
  • >= 2.4.7-beta1, < 2.4.7-p3 2.4.7-p3
    composer require magento/community-edition:2.4.7-p3

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

As a temporary workaround, restrict access to the affected components of your application and monitor for any suspicious activity. Additionally, consider implementing network-level controls to limit outbound requests from your Magento installation.

Conclusion

The SSRF vulnerability in Magento Community Edition poses a significant risk to the security of affected installations. It is crucial for users to update to the latest patched versions to mitigate this risk. Regular monitoring and adherence to security best practices are essential to protect against such vulnerabilities.

See every vulnerability recorded for magento/community-edition →

Share this vulnerability

FAQ

The CVSS score of this vulnerability is 5.5, indicating a moderate severity level.

The affected versions include Magento Community Edition 2.4.7-p2, 2.4.6-p7, 2.4.5-p9, 2.4.4-p10 and earlier.

No, exploitation of this vulnerability does not require user interaction.

You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. You can check your application using the Vulert playground at Vulert Scanner without any signup.

Exploitation of this vulnerability can lead to unauthorized access to sensitive files, compromising the confidentiality and integrity of your application.

Related vulnerabilities

Recent vulnerabilities recorded for magento/community-edition.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • < 2.4.4-p11 2.4.4-p11
    composer require magento/community-edition:2.4.4-p11
  • >= 2.4.5-p1, < 2.4.5-p10 2.4.5-p10
    composer require magento/community-edition:2.4.5-p10
  • >= 2.4.6-p1, < 2.4.6-p8 2.4.6-p8
    composer require magento/community-edition:2.4.6-p8
  • >= 2.4.7-beta1, < 2.4.7-p3 2.4.7-p3
    composer require magento/community-edition:2.4.7-p3

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback