dbcve.org
MagentoCMS

CVE-2019-7951

HIGH · 7.5 CVSS v3.0 Published 2019-08-02
Fix available
A fix is available. Upgrade to 2.1.18 / 2.2.9 or later.
See remediation →
84/100
Remediation priority · High
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 information leakage vulnerability exists 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. A SOAP web service endpoint does not properly enforce parameters related to access control. This could be abused to leak customer information via crafted SOAP requests.

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

Magento's SOAP web service endpoint fails to properly enforce access control parameters, allowing attackers to craft malicious SOAP requests that bypass authorization checks and leak sensitive customer information such as PII, addresses, and order history.

MitigationApply the vendor security patches (Magento 2.1.18, 2.2.9, or 2.3.2 or later) to resolve the improper access control enforcement in the SOAP API, and audit SOAP endpoint logs for signs of exploitation.

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.1.0, < 2.1.18>= 2.2.0, < 2.2.9>= 2.3.0, < 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
None
Availability
None

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

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 Magento installed version
    Run the command 'php bin/magento --version' from the Magento root directory, or check the file 'composer.json' for the 'version' field under the 'magento/product-community-edition' or 'magento/product-enterprise-edition' package.
    Affected if The installed version falls within any of these ranges: >= 2.1.0 and < 2.1.18, OR >= 2.2.0 and < 2.2.9, OR >= 2.3.0 and < 2.3.2
  2. Verify SOAP API module is enabled
    Check the output of 'php bin/magento module:status' for the 'Magento_WebapiSoap' module, or inspect the configuration file 'app/etc/config.php' for the value 'Magento_WebapiSoap' set to '1'.
    Affected if The SOAP API module (Magento_WebapiSoap) is enabled on an affected Magento version.
  3. Review SOAP endpoint access logs
    Inspect the log files in the 'var/log/' directory, specifically 'debug.log' and any custom SOAP access logs, for API requests to endpoints under '/soap' or '/api.soap'. Look for requests from unauthorized user IDs or API keys.
    Affected if There are SOAP API requests using credentials or tokens that should not have access to customer data, or requests accessing customer endpoints without proper authorization headers.
  4. Check for anomalous customer data retrieval patterns
    Query the database table 'enterprise_logging_log' or the API access logs for repeated or bulk requests to customer-related SOAP API methods such as 'customerCustomerRepositoryV1', 'customerAddressRepositoryV1', or 'salesOrderRepositoryV1' from single API credentials.
    Affected if Single API credentials are retrieving unusually high volumes of customer PII, addresses, or order data beyond normal business usage patterns.
  5. Audit SOAP API user roles and permissions
    Review the user roles configured for SOAP API access in the Magento Admin panel under 'System > Permissions > API Users' and verify that role ACLs do not grant excessive customer data access, or check the 'authorization_rule' table in the database for overly permissive rules on SOAP-connected roles.
    Affected if SOAP API users have roles with overly broad ACLs that grant access to customer PII, addresses, or orders beyond what their job function requires.

Your environment is affected if you run any Magento version between 2.1.0 and 2.1.17, between 2.2.0 and 2.2.8, or between 2.3.0 and 2.3.1, with the SOAP API module enabled and accessible.

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.1.18 / 2.2.9 / 2.3.2 or later
Fixed in 2.1.182.2.92.3.2
Interim mitigation

Apply the vendor security patches (Magento 2.1.18, 2.2.9, or 2.3.2 or later) to resolve the improper access control enforcement in the SOAP API, and audit SOAP endpoint logs for signs of exploitation.

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-7951 — 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-7951 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