CVE-2023-38249: Magento Community Edition SQL Injection Vulnerability

magento/community-edition Updated 02 Oct 2025

Summary

13/10/2023
Yes i
Moderate
8.0

CVE-2023-38249: Magento Open Source allows SQL Injection. Affects magento/community-edition across 4 version ranges.

>= 2.4.4-p1, < 2.4.4-p6 >= 2.4.5-p1, < 2.4.5-p5 >= 2.4.6-p1, < 2.4.6-p3 >= 2.4.7-beta1, < 2.4.7-beta2

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 Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

Magento Community Edition is a widely used open-source eCommerce platform that enables businesses to create and manage online stores. It offers a range of features including product management, customer management, and order processing. However, certain versions of Magento are susceptible to SQL injection vulnerabilities, which can compromise the security of the application and its data.

Vulnerability Detail

Adobe Commerce versions 2.4.7-beta1 and earlier, 2.4.6-p2 and earlier, 2.4.5-p4 and earlier, and 2.4.4-p5 and earlier are affected by an SQL Injection vulnerability. This flaw arises from improper neutralization of special elements used in SQL commands, allowing an authenticated attacker with admin privileges to execute arbitrary code. The exploitation does not require user interaction, but it necessitates advanced knowledge of tooling beyond the standard user interface. The CVSS score for this vulnerability is 8.0, indicating a high severity level.

How To Fix

Fixed versions by release line

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

  • >= 2.4.4-p1, < 2.4.4-p6 2.4.4-p6
    composer require magento/community-edition:2.4.4-p6
  • >= 2.4.5-p1, < 2.4.5-p5 2.4.5-p5
    composer require magento/community-edition:2.4.5-p5
  • >= 2.4.6-p1, < 2.4.6-p3 2.4.6-p3
    composer require magento/community-edition:2.4.6-p3
  • >= 2.4.7-beta1, < 2.4.7-beta2 2.4.7-beta2
    composer require magento/community-edition:2.4.7-beta2

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

Workaround

If immediate patching is not possible, consider restricting access to the admin panel to trusted IP addresses only, thereby reducing the risk of exploitation. Additionally, ensure that your application is monitored for unusual activities.

Conclusion

The SQL Injection vulnerability in Magento Community Edition poses a significant risk to users, particularly those with admin access. It is essential to update to the latest patched versions to mitigate this risk. Utilizing tools like Vulert can help in monitoring and identifying vulnerabilities in your applications effectively.

See every vulnerability recorded for magento/community-edition →

Share this vulnerability

FAQ

SQL Injection is a type of security vulnerability that allows an attacker to interfere with the queries that an application makes to its database.

You can check if your application is affected by using Vulert, which monitors open-source vulnerabilities in real-time. Visit Vulert Scanner to analyze your composer.lock file.

Exploitation of this vulnerability can lead to unauthorized access, data breaches, and potential control over the affected system.

Yes, it is crucial to update to the patched versions as soon as possible to protect your application from potential attacks.

Yes, Vulert allows you to check for vulnerabilities without requiring an account, making it easy to monitor your applications.

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-p1, < 2.4.4-p6 2.4.4-p6
    composer require magento/community-edition:2.4.4-p6
  • >= 2.4.5-p1, < 2.4.5-p5 2.4.5-p5
    composer require magento/community-edition:2.4.5-p5
  • >= 2.4.6-p1, < 2.4.6-p3 2.4.6-p3
    composer require magento/community-edition:2.4.6-p3
  • >= 2.4.7-beta1, < 2.4.7-beta2 2.4.7-beta2
    composer require magento/community-edition:2.4.7-beta2

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