CVE-2019-8154: Magento remote code execution vulnerability

magento/community-edition Updated 02 Oct 2025

Summary

24/05/2022
Yes i
High
8.8

CVE-2019-8154: Magento remote code execution vulnerability. Affects magento/community-edition across 2 version ranges.

>= 2.2.0, < 2.2.10 >= 2.3.0, < 2.3.2-p2

Fixed in 2.2.10 or 2.3.2-p2, depending 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

Magento is an open-source e-commerce platform used for building online stores. It provides a wide range of features for managing product catalogs, customer orders, and payment processing. The vulnerability identified as CVE-2019-8154 affects Magento versions 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3, or 2.3.2-p1. This vulnerability allows an authenticated user with privileges to modify product catalogs to trigger PHP file inclusion through a crafted XML file that specifies product design update.

Vulnerability Detail

The CVE-2019-8154 vulnerability in Magento allows an attacker with authenticated access and product catalog modification privileges to execute arbitrary PHP code remotely. By exploiting a flaw in the XML file parsing mechanism, an attacker can include malicious PHP files, leading to remote code execution. This vulnerability poses a significant risk as it allows an attacker to gain control over the affected Magento installation, potentially compromising customer data, and performing unauthorized actions.

How To Fix

Fixed versions by release line

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

  • >= 2.2.0, < 2.2.10 2.2.10
    composer require magento/community-edition:2.2.10
  • >= 2.3.0, < 2.3.2-p2 2.3.2-p2
    composer require magento/community-edition:2.3.2-p2

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

Workaround

There is no known workaround for this vulnerability. It is crucial to apply the recommended patches or upgrade to the latest secure versions of Magento to address the issue.

Conclusion

The CVE-2019-8154 vulnerability in Magento poses a significant risk to affected installations. It allows an attacker to execute arbitrary PHP code remotely, potentially compromising customer data and performing unauthorized actions. To mitigate this risk, it is crucial to apply the recommended patches or upgrade to the latest secure versions of Magento. For further support on vulnerability remediation, you can contact DevNack.com.

See every vulnerability recorded for magento/community-edition →

Share this vulnerability

FAQ

This vulnerability allows an attacker to execute arbitrary PHP code remotely, potentially compromising the affected Magento installation, customer data, and performing unauthorized actions.

Magento versions 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3, and 2.3.2-p1 are affected by this vulnerability. Users of these versions should upgrade to the latest patched versions.

You can use the Vulert Playground (https://vulert.com/scanner) to check if your Magento installation is affected by this vulnerability. Simply upload your composer.lock file to the playground, and it will alert you if any open-source vulnerabilities, including CVE-2019-8154, are detected.

At the time of this report, there are no known public exploits specifically targeting this vulnerability. However, it is crucial to apply the recommended patches or upgrade to the latest secure versions to mitigate the risk.

You can find more information about this vulnerability, including the technical details and the recommended fixes, in the GitHub Advisory Database: https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2022/05/GHSA-4v2q-hjx3-c4vr/GHSA-4v2q-hjx3-c4vr.json

Related vulnerabilities

Recent vulnerabilities recorded for magento/community-edition.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Fixed versions by release line

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

  • >= 2.2.0, < 2.2.10 2.2.10
    composer require magento/community-edition:2.2.10
  • >= 2.3.0, < 2.3.2-p2 2.3.2-p2
    composer require magento/community-edition:2.3.2-p2

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