CVE-2019-8137: Magento 2 Community Edition RCE 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 manipulate CMS section of the website can trigger remote code execution via custom layout update.

Other sources

Magento 2 Community Edition RCE Vulnerability

— Packagist

PRODSECBUG-2414: Remote code execution through custom layout update of the content management functionality

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-p1
2.3.2-p1
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-p1
2.3.2-p1
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-p1
  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

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:19 PM
Data Sourced
via MITRE·11:19 PM
DescriptionWeakness
Nov 6, 2019
Data Sourced
via NVD·12:15 AM
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-8137?

CVE-2019-8137 is classified as a remote code execution vulnerability that can potentially allow an attacker to execute arbitrary code on affected systems.

2

How do I fix CVE-2019-8137?

To fix CVE-2019-8137, upgrade Magento to version 2.2.10 or 2.3.2-p1 or later versions.

3

Who is affected by CVE-2019-8137?

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

4

What are the implications of CVE-2019-8137?

The implications of CVE-2019-8137 include the potential for unauthorized access and control over the Magento eCommerce platform.

5

Can CVE-2019-8137 be exploited remotely?

Yes, CVE-2019-8137 can be exploited remotely by authenticated users with specific privileges.

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