dbcve.org
MagentoCMS

CVE-2019-8156

HIGH · 7.2 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 →
78/100
Remediation priority · High
Remotely reachable 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
A server-side request forgery (SSRF) 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 authenticated user with admin privileges to modify store configurations can manipulate the connector api endpoint to enable remote code execution.

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 a server-side request forgery (SSRF) vulnerability in Magento 2's connector API endpoint. An authenticated administrator with privileges to modify store configurations can manipulate the connector API to make the server perform unintended requests, leading to remote code execution. The vulnerability requires admin-level authentication, combining privilege escalation with SSRF-to-RCE.

MitigationUpgrade Magento to version 2.2.10+, 2.3.3, or 2.3.2-p1 or higher. As a compensating control, restrict admin panel access to trusted personnel only and monitor for unusual API endpoint activity.

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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. Identify the installed Magento version
    Run `php bin/magento --version` from the Magento root directory, or inspect the `composer.json` file for the `magento/product-community-edition` or `magento/product-enterprise-edition` version entry
    Affected if The installed version falls within 2.2.0 to 2.2.9, 2.3.0 to 2.3.2 (including 2.3.2 exactly)
  2. Verify the connector API module status
    Run `php bin/magento module:status` to list enabled modules, specifically look for `Magento_Connector` or related integration modules under `Magento_Integration`
    Affected if The connector module is enabled (this is the default state in affected versions)
  3. Check admin user privileges for API integration access
    Navigate to System > Integrations in the admin panel, or query the `admin_user` and `authorization_role` tables in the Magento database to identify users with elevated privileges
    Affected if Any admin user with permissions to modify store configurations or manage API integrations exists in the system
  4. Inspect API endpoint configuration
    Review the web server logs for access to endpoints under `/rest/` or `/api/` paths, particularly integration-related endpoints. Check `app/etc/config.php` for enabled integration modules
    Affected if The REST API and connector endpoints are publicly accessible without additional network restrictions
  5. Confirm admin panel accessibility
    Attempt to access the admin login page at the standard `/admin` or custom admin path, or check the `app/etc/env.php` file for the `backend` frontName setting
    Affected if The admin panel is reachable from the network without strong access controls

You are affected if your Magento 2 installation runs version 2.2.0 through 2.2.9, 2.3.0 through 2.3.1, or exactly 2.3.2, the connector API module is enabled, and admin users with store configuration privileges can access the admin panel.

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.

From vendor data
Upgrade available Upgrade to 2.2.10 / 2.3.2 or later
Fixed in 2.2.102.3.2
Interim mitigation

Upgrade Magento to version 2.2.10+, 2.3.3, or 2.3.2-p1 or higher. As a compensating control, restrict admin panel access to trusted personnel only and monitor for unusual API endpoint activity.

Fix this in Magento Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-8156 — 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-8156 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