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

Published Jun 25, 2019
·
Updated

Insufficient input validation in the config builder of the Elastic search module could lead to remote code execution in Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2. This vulnerability could be abused by an authenticated user with the ability to configure the catalog search.

Other sources

Magento 2 Community Edition RCE Vulnerability

— Packagist

PRODSECBUG-2266: Arbitrary code execution through malicious elastic search module configuration

Affected Software

13 affected componentsFixes available
composer/magento/product-community-edition>=2.1, <2.1.18, >=2.2, <2.2.9, >=2.3, <2.3.2
composer/magento/community-edition>=2.3<2.3.2
2.3.2
composer/magento/community-edition>=2.2<2.2.9
2.2.9
composer/magento/community-edition>=2.1<2.1.18
2.1.18
Magento Magento>=2.1.0<2.1.18
Magento Magento>=2.2.0<2.2.9
Magento Magento>=2.3.0<2.3.2
composer/magento/community-edition>=2.3, <2.3.2
2.3.2
composer/magento/community-edition>=2.2, <2.2.9
2.2.9
composer/magento/community-edition>=2.1, <2.1.18
2.1.18
composer/magento/product-community-edition>=2.1, <2.1.18
2.1.18
composer/magento/product-community-edition>=2.2, <2.2.9
2.2.9
composer/magento/product-community-edition>=2.3, <2.3.2
2.3.2

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
  2. Upgrade

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

    Fixed in 2.2.9
  3. Upgrade

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

    Fixed in 2.1.18
  4. Upgrade

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

    Fixed in 2.1.18
  5. Upgrade

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

    Fixed in 2.2.9
  6. Upgrade

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

    Fixed in 2.3.2
  7. Upgrade

    Upgrade Magento 2.1 to a version that resolves this vulnerability.

    Fixed in 2.1.18Patch PRODSECBUG-2266
  8. Upgrade

    Upgrade Magento 2.2 to a version that resolves this vulnerability.

    Fixed in 2.2.9Patch PRODSECBUG-2266
  9. Upgrade

    Upgrade Magento 2.3 to a version that resolves this vulnerability.

    Fixed in 2.3.2Patch PRODSECBUG-2266

Event History

Jun 25, 2019
Advisory Published
12:00 AM
Data Sourced
via Packagist·12:00 AM
DescriptionSeverityAffected Software
Aug 2, 2019
CVE Published
via MITRE·09:20 PM
Data Sourced
via MITRE·09:20 PM
DescriptionWeakness
Data Sourced
via NVD·10:15 PM
DescriptionSeverityWeaknessAffected Software
May 24, 2022
Advisory Published
via GitHub·04:52 PM
Data Sourced
via GitHub·04:52 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2019-7885?

CVE-2019-7885 is considered a critical vulnerability due to its potential for remote code execution.

2

How do I fix CVE-2019-7885?

To fix CVE-2019-7885, upgrade your Magento instance to version 2.1.18, 2.2.9, or 2.3.2 or later.

3

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

CVE-2019-7885 affects Magento versions 2.1.x prior to 2.1.18, 2.2.x prior to 2.2.9, and 2.3.x prior to 2.3.2.

4

Can CVE-2019-7885 be exploited by unauthenticated users?

CVE-2019-7885 requires authentication to exploit, specifically by users with the ability to configure the Elasticsearch module.

5

What is the impact of CVE-2019-7885 on Magento users?

The impact of CVE-2019-7885 includes the potential for attackers to execute arbitrary code on affected Magento installations.

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