CVE-2019-7139: Magento 2 Community Edition SQLi Vulnerability

Published Mar 26, 2019
·
Updated

An unauthenticated user can execute SQL statements that allow arbitrary read access to the underlying database, which causes sensitive data leakage. This issue is fixed 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.

Other sources

Magento 2 Community Edition SQLi Vulnerability

— Packagist

PRODSECBUG-2198: SQL Injection due to a flaw in MySQL adapter

SUPEE-11086 - RCE, XSS, CSRF and other vulnerabilities

Affected Software

20 affected componentsFixes available
composer/magento/magento1ee>=1.9.0.0, <1.14.4.1
composer/magento/magento1ce>=1.5.0.0, <1.9.4.1
composer/magento/product-community-edition>=2.1, <2.1.18
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<1.9.4.1
Magento Magento>=1.14.0.0<1.14.4.1
Magento Magento>=2.1.0<2.1.17
Magento Magento>=2.1.0<2.1.17
Magento Magento>=2.2.0<2.2.8
Magento Magento>=2.2.0<2.2.8
Magento Magento>=2.3.0<2.3.1
Magento Magento>=2.3.0<2.3.1
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/magento1ee>=1.9.0.0, <1.14.4.1
1.14.4.1
composer/magento/magento1ce>=1.5.0.0, <1.9.4.1
1.9.4.1

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/magento1ee to a version that resolves this vulnerability.

    Fixed in 1.14.4.1
  6. Upgrade

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

    Fixed in 1.9.4.1
  7. Upgrade

    Upgrade Magento 2 Community Edition to a version that resolves this vulnerability.

    Fixed in 2.1.18
  8. Upgrade

    Upgrade Magento 2 Community Edition to a version that resolves this vulnerability.

    Fixed in 2.2.9
  9. Upgrade

    Upgrade Magento 2 Community Edition to a version that resolves this vulnerability.

    Fixed in 2.3.2

Event History

Mar 26, 2019
Advisory Published
12:00 AM
Data Sourced
via Packagist·12:00 AM
DescriptionSeverityAffected Software
Apr 10, 2019
CVE Published
via MITRE·05:07 PM
Data Sourced
via MITRE·05:07 PM
DescriptionWeakness
Data Sourced
via NVD·06:29 PM
DescriptionSeverityWeaknessAffected Software
May 24, 2022
Advisory Published
via GitHub·10:00 PM
Data Sourced
via GitHub·10:00 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2019-7139?

CVE-2019-7139 has a critical severity rating due to its potential for sensitive data leakage.

2

How do I fix CVE-2019-7139?

To fix CVE-2019-7139, upgrade to Magento versions 2.1.18, 2.2.9, or 2.3.2 or later.

3

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

CVE-2019-7139 affects Magento versions prior to 2.1.18, 2.2.9, and 2.3.2.

4

Is CVE-2019-7139 an authenticated or unauthenticated vulnerability?

CVE-2019-7139 is an unauthenticated vulnerability, allowing attackers to execute SQL statements.

5

What type of vulnerability is CVE-2019-7139 classified as?

CVE-2019-7139 is classified as an SQL injection vulnerability.

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