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

> An attacker can exploit an XPath entity injection in Magento's page cache module to access underlying XML data via crafted GET requests.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Nov 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8p5c-f836-m4h7

## What is CVE-2019-8158?

CVE-2019-8158 is a critical vulnerability in Magento Magento, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-91 (XML Injection)

## Which versions are affected by CVE-2019-8158?

4 open source packages ship an affected version, including magento/community-edition. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `magento/community-edition` | Packagist | From 2.2.0 | 2.2.10 |
| `magento/community-edition` | Packagist | From 2.2.0 | 2.2.10 |
| `magento/community-edition` | Packagist | From 2.3.0 | 2.3.2-p2 |
| `magento/community-edition` | Packagist | From 2.3.0 | 2.3.2-p2 |

Products: Magento Magento.

## How do I fix CVE-2019-8158?

Upgrade magento/community-edition to a fixed version for your release line: 2.2.10 or 2.3.2-p2.

## Is CVE-2019-8158 being exploited?

There is no known exploitation of CVE-2019-8158 in the wild and no public exploit code.

## Other vulnerabilities in Magento Magento

- [CVE-2020-9664](https://insights.sbomify.com/CVE-2020-9664/): Magento php object injection vulnerability (critical 9.8)
- [CVE-2020-9576](https://insights.sbomify.com/CVE-2020-9576/): Magento command injection vulnerability (critical 9.8)
- [CVE-2020-9578](https://insights.sbomify.com/CVE-2020-9578/): Magento command injection vulnerability (critical 9.8)
- [CVE-2020-9579](https://insights.sbomify.com/CVE-2020-9579/): Magento Security mitigation bypass vulnerability (critical 9.8)
- [CVE-2020-9580](https://insights.sbomify.com/CVE-2020-9580/): Magento Security mitigation bypass vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-8158 and fix it if it is affected.

What it is: CVE-2019-8158 is a critical vulnerability in Magento Magento, published on 6 Nov 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-8158 in the wild and no public exploit code.

Affected packages and fixed versions:
- magento/community-edition (Packagist): affected from 2.2.0; fixed in 2.2.10
- magento/community-edition (Packagist): affected from 2.2.0; fixed in 2.2.10
- magento/community-edition (Packagist): affected from 2.3.0; fixed in 2.3.2-p2
- magento/community-edition (Packagist): affected from 2.3.0; fixed in 2.3.2-p2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2019-8158/ (Markdown: https://insights.sbomify.com/CVE-2019-8158/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2019-8158
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2019-8158
- OSV: https://osv.dev/vulnerability/CVE-2019-8158

---
From sbomify Insights: https://insights.sbomify.com/CVE-2019-8158/
Summaries are generated and may contain mistakes; the official description above is the record.