CVE-2019-8154: Magento remote code execution vulnerability

Published Oct 8, 2019
·
Updated

A remote code execution vulnerability exists in Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3 or 2.3.2-p1. An authenticated user with privileges to modify product catalogs can trigger PHP file inclusion through a crafted XML file that specifies product design update.

Other sources

Magento remote code execution vulnerability

— Packagist

PRODSECBUG-2332: Remote code execution through arbitrary file inclusion

Affected Software

13 affected componentsFixes available
composer/magento/product-community-edition>=2.2, <2.2.10, >=2.3, <2.3.2-p2
composer/magento/community-edition>=2.3.0<2.3.2-p2
2.3.2-p2
composer/magento/community-edition>=2.2.0<2.2.10
2.2.10
Magento Magento>=2.2.0<2.2.10
Magento Magento>=2.2.0<2.2.10
Magento Magento>=2.3.0<2.3.2
Magento Magento>=2.3.0<2.3.2
Magento Magento=2.3.2
Magento Magento=2.3.2
composer/magento/community-edition>=2.3.0, <2.3.2-p2
2.3.2-p2
composer/magento/community-edition>=2.2.0, <2.2.10
2.2.10
composer/magento/product-community-edition>=2.2, <2.2.10
2.2.10
composer/magento/product-community-edition>=2.3, <2.3.2-p2
2.3.2-p2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.3.2-p2
  2. Upgrade

    Upgrade composer/magento/community-edition to a version that resolves this vulnerability.

    Fixed in 2.2.10
  3. Upgrade

    Upgrade composer/magento/product-community-edition to a version that resolves this vulnerability.

    Fixed in 2.2.10
  4. Upgrade

    Upgrade composer/magento/product-community-edition to a version that resolves this vulnerability.

    Fixed in 2.3.2-p2
  5. Upgrade

    Upgrade Magento 2.2 to a version that resolves this vulnerability.

    Fixed in 2.2.10
  6. Upgrade

    Upgrade Magento 2.3 to a version that resolves this vulnerability.

    Fixed in 2.3.3
  7. Upgrade

    Upgrade Magento 2.3 to a version that resolves this vulnerability.

    Fixed in 2.3.2-p2

Event History

Oct 8, 2019
Advisory Published
12:00 AM
Data Sourced
via Packagist·12:00 AM
DescriptionSeverityAffected Software
Nov 5, 2019
CVE Published
via MITRE·11:50 PM
Data Sourced
via MITRE·11:50 PM
DescriptionWeakness
Nov 6, 2019
Data Sourced
via NVD·12:15 AM
RemedyDescriptionSeverityWeaknessAffected Software
May 24, 2022
Advisory Published
via GitHub·10:01 PM
Data Sourced
via GitHub·10:01 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2019-8154?

CVE-2019-8154 has a high severity rating due to its potential for remote code execution.

2

How do I fix CVE-2019-8154?

To mitigate CVE-2019-8154, upgrade your Magento installation to version 2.2.10 or 2.3.3 and above.

3

Which versions are affected by CVE-2019-8154?

CVE-2019-8154 affects Magento 2.2 versions prior to 2.2.10 and Magento 2.3 versions prior to 2.3.3 or 2.3.2-p1.

4

Can an unauthenticated user exploit CVE-2019-8154?

No, exploitation of CVE-2019-8154 requires an authenticated user with the ability to modify product catalogs.

5

What type of attack does CVE-2019-8154 facilitate?

CVE-2019-8154 facilitates a remote code execution attack through PHP file inclusion from a crafted XML file.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203