CVE-2019-7911: Magento 2 Community Edition Server-Side Request Forgery vulnerability

Published Jun 25, 2019
·
Updated

A server-side request forgery (SSRF) vulnerability exists in Magento Open Source prior to 1.9.4.2, and Magento Commerce prior to 1.14.4.2, 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 can be exploited by an authenticated user with access to the admin panel to manipulate system configuration and execute arbitrary code.

Other sources

Magento 2 Community Edition Server-Side Request Forgery vulnerability

— Packagist

PRODSECBUG-2320: Arbitrary code execution due to unsafe handling of system configuration

Affected Software

17 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/magento1ee>=1, <1.14.4.2
composer/magento/magento1ce>=1, <1.9.4.2
composer/magento/community-edition>=2.3.0<2.3.2
2.3.2
composer/magento/community-edition>=2.2.0<2.2.9
2.2.9
composer/magento/community-edition>=2.1.0<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.0, <2.3.2
2.3.2
composer/magento/community-edition>=2.2.0, <2.2.9
2.2.9
composer/magento/community-edition>=2.1.0, <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
composer/magento/magento1ee>=1, <1.14.4.2
1.14.4.2
composer/magento/magento1ce>=1, <1.9.4.2
1.9.4.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 composer/magento/magento1ee to a version that resolves this vulnerability.

    Fixed in 1.14.4.2
  8. Upgrade

    Upgrade composer/magento/magento1ce to a version that resolves this vulnerability.

    Fixed in 1.9.4.2
  9. Upgrade

    Upgrade Magento Open Source to a version that resolves this vulnerability.

    Fixed in 1.9.4.2
  10. Upgrade

    Upgrade Magento Commerce to a version that resolves this vulnerability.

    Fixed in 1.14.4.2
  11. Upgrade

    Upgrade Magento 2.1 to a version that resolves this vulnerability.

    Fixed in 2.1.18
  12. Upgrade

    Upgrade Magento 2.2 to a version that resolves this vulnerability.

    Fixed in 2.2.9
  13. Upgrade

    Upgrade Magento 2.3 to a version that resolves this vulnerability.

    Fixed in 2.3.2

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:26 PM
Data Sourced
via MITRE·09:26 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-7911?

CVE-2019-7911 has a high severity rating due to its potential for enabling server-side request forgery attacks.

2

How do I fix CVE-2019-7911?

To mitigate CVE-2019-7911, upgrade to Magento Open Source versions 1.9.4.2 or later, Magento Commerce 1.14.4.2 or later, Magento 2.1.18 or later, 2.2.9 or later, or 2.3.2 or later.

3

Who is affected by CVE-2019-7911?

Authenticated users with access to the admin panel of affected versions of Magento are vulnerable to CVE-2019-7911.

4

What types of Magento are impacted by CVE-2019-7911?

CVE-2019-7911 impacts Magento Open Source and Magento Commerce versions prior to the specified patched versions.

5

Is there a known exploit for CVE-2019-7911?

Yes, CVE-2019-7911 can be exploited through crafted requests by authenticated users with administrative access.

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