CVE-2019-8119: Magento 2 Community Edition RCE Vulnerability

Published Oct 8, 2019
·
Updated

A remote code execution vulnerability exists in Magento 2.1 prior to 2.1.19, Magento 2.2 prior to 2.2.10, Magento 2.3 prior to 2.3.3. An authenticated admin user with import product privileges can delete files through bulk product import and inject code into XSLT file. The combination of these manipulations can lead to remote code execution.

Other sources

Magento 2 Community Edition RCE Vulnerability

— Packagist

PRODSECBUG-2449: Remote code execution via local file delete and XSLT injection

Affected Software

15 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.3
2.3.3
composer/magento/community-edition>=2.2.0<2.2.10
2.2.10
composer/magento/community-edition>=2.1.0<2.1.19
2.1.19
Magento Magento>=2.1.0<2.1.19
Magento Magento>=2.1.0<2.1.19
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
composer/magento/community-edition>=2.3.0, <2.3.3
2.3.3
composer/magento/community-edition>=2.2.0, <2.2.10
2.2.10
composer/magento/community-edition>=2.1.0, <2.1.19
2.1.19
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.3
  2. Upgrade

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

    Fixed in 2.2.10
  3. Upgrade

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

    Fixed in 2.1.19
  4. Upgrade

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

    Fixed in 2.2.10
  5. Upgrade

    Upgrade composer/magento/product-community-edition 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·10:49 PM
Data Sourced
via MITRE·10:49 PM
DescriptionWeakness
Data Sourced
via NVD·11:15 PM
RemedyDescriptionSeverityAffected Software
May 24, 2022
Advisory Published
via GitHub·05:00 PM
Data Sourced
via GitHub·05:00 PM
DescriptionSeverityAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2019-8119?

CVE-2019-8119 is classified as a critical vulnerability due to its potential for remote code execution.

2

Which versions of Magento are affected by CVE-2019-8119?

CVE-2019-8119 affects Magento 2.1 versions prior to 2.1.19, Magento 2.2 prior to 2.2.10, and Magento 2.3 prior to 2.3.3.

3

How do I fix CVE-2019-8119?

To fix CVE-2019-8119, upgrade Magento to version 2.3.3, 2.2.10, or 2.1.19 or later.

4

What type of attack does CVE-2019-8119 enable?

CVE-2019-8119 enables an authenticated administrator to perform remote code execution through bulk product import.

5

Who can exploit CVE-2019-8119?

Only authenticated admin users with import product privileges can exploit CVE-2019-8119.

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