dbcve.org
MagentoCMS

CVE-2019-8158

CRITICAL · 9.8 CVSS v3.1 Published 2019-11-06
Fix available
A fix is available. Upgrade to 2.2.10 / 2.3.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an XPath entity injection vulnerability in Magento 2.2 and 2.3's page cache block rendering module. Attackers can craft malicious GET request parameters containing XPath injection payloads that get passed to the XML data processing engine without validation, allowing limited read access to underlying XML data structures.

MitigationApply the vendor-supplied security patches (PRODSECBUG-2198) or upgrade to Magento 2.2.10, 2.3.2-p1, or 2.3.3 or later to remediate this vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MagentoCMS
Affected:>= 2.2.0, < 2.2.10>= 2.3.0, < 2.3.2= 2.3.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Determine your Magento installation version
    Run `bin/magento --version` from the Magento root directory, or check the `composer.lock` file for the `magento/product-community-edition` package version, or view the version in the Magento Admin panel under System > Configuration > General > Advanced > Developer > Advanced Settings
    Affected if The installed version is >= 2.2.0 and < 2.2.10, OR >= 2.3.0 and <= 2.3.2 (including 2.3.2 itself)
  2. Verify the Page Cache module is enabled
    Check the file `app/etc/config.php` for the line `'Magento_PageCache' => 1` or run `bin/magento module:status Magento_PageCache` to confirm the module is enabled
    Affected if The Magento_PageCache module is enabled (value is 1 in config.php)
  3. Identify the vulnerable XML processing component
    Locate the page cache block rendering code in `vendor/magento/module-page-cache/Model/Block.php` or the equivalent path in the installation, specifically any code that processes XML from request parameters
    Affected if The file exists and contains XPath query processing without input validation on GET parameters
  4. Inspect request parameter handling in the block rendering logic
    Review the code that handles block rendering with XML data. Look for XPath or XML processing that directly uses GET parameters (such as `$_GET` or `$request->getParams()`) without sanitization
    Affected if The code passes unsanitized GET parameters directly to XPath query functions like `xpath()` or DOMXPath

You are affected if your Magento version falls within 2.2.0 to 2.2.9, or 2.3.0 to 2.3.2, AND the Page Cache module is enabled and processes XML from request parameters.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 2.2.10 / 2.3.2 or later
Fixed in 2.2.102.3.2
Interim mitigation

Apply the vendor-supplied security patches (PRODSECBUG-2198) or upgrade to Magento 2.2.10, 2.3.2-p1, or 2.3.3 or later to remediate this vulnerability.

Recommended fix High confidence

Magento 2.2.10+ or 2.3.3+ (or 2.3.2-p1)

  1. 1. Backup your Magento database and filesystem before proceeding
  2. 2. For Magento 2.2.x: Upgrade to version 2.2.10 or later
  3. 3. For Magento 2.3.x: Upgrade to version 2.3.3 or later (or 2.3.2-p1 if available for your branch)
  4. 4. Clear Magento cache after upgrade: bin/magento cache:flush
  5. 5. Reindex if necessary: bin/magento indexer:reindex
  6. 6. Verify the patch is applied by checking Magento version: bin/magento --version
Caveat Review Magento release notes for breaking changes between your current version and target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Magento Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-8158 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-8158 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data