CVE-2019-8158: Magento 2 Community Edition XML Injection

Published Oct 8, 2019
·
Updated

An XPath entity injection 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 attacker can craft a GET request to page cache block rendering module that gets passed to XML data processing engine without validation. The crafted key/value GET request data allows an attacker to limited access to underlying XML data.

Other sources

Magento 2 Community Edition XML Injection

— Packagist

PRODSECBUG-2272: XPath Injection via front end rendering 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-p2
2.3.2-p2
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-p2
2.3.2-p2
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-p2
  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
  7. Upgrade

    Upgrade Magento 2.3.2 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 6, 2019
CVE Published
via MITRE·12:03 AM
Data Sourced
via MITRE·12:03 AM
DescriptionWeakness
Data Sourced
via NVD·01:15 AM
DescriptionSeverityWeaknessAffected Software
May 24, 2022
Advisory Published
via GitHub·05:00 PM
Data Sourced
via GitHub·05:00 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2019-8158?

CVE-2019-8158 is rated as a medium severity vulnerability due to the potential for XPath entity injection.

2

How do I fix CVE-2019-8158?

To fix CVE-2019-8158, upgrade Magento to version 2.2.10 or 2.3.3 and higher.

3

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

CVE-2019-8158 affects Magento versions 2.2.0 to 2.2.9 and 2.3.0 to 2.3.2.

4

Can I check if my Magento site is vulnerable to CVE-2019-8158?

You can check your Magento version against the affected ranges to determine if your site is vulnerable to CVE-2019-8158.

5

What types of attacks can be executed due to CVE-2019-8158?

CVE-2019-8158 allows attackers to exploit unvalidated input leading to potential XPath entity injection attacks.

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