CVE-2019-7892
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 · uneditedA remote code execution 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. An authenticated user with administrator privileges to access shipment settings can execute arbitrary code via server-side request forgery.
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 confidenceThis is an authenticated remote code execution vulnerability in Magento 2.x. An attacker with administrator-level access to shipment settings can exploit a server-side request forgery (SSRF) flaw to execute arbitrary code on the underlying server. The vulnerability stems from insufficient validation of user-supplied input in the shipment configuration functionality, allowing the authenticated admin to make the server perform unintended requests to internal or external resources and potentially achieve RCE.
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>= 2.1.0, < 2.1.18>= 2.2.0, < 2.2.9>= 2.3.0, < 2.3.2CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Determine installed Magento 2 versionCheck the version file in your Magento installation directory, typically in composer.json or lib/internal/Magento/Framework/App/ProductMetadata.php. Run: composer show magento/product-community-edition 2>&1 or grep -r '"version"' composer.json | head -5Affected if The installed version falls within < 2.1.18, < 2.2.9, or < 2.3.2 for their respective branches (2.1.x, 2.2.x, 2.3.x)
-
Confirm admin access to shipment settings existsLog into the Magento admin panel and navigate to Stores > Settings > Shipment Settings, or check if the /admin/shipping/ or similar shipment configuration endpoints are accessibleAffected if Administrator-level credentials exist and the shipment configuration interface is reachable without additional access controls
-
Verify shipment configuration functionality is enabledCheck if shipment methods are configured in Stores > Configuration > Sales > Shipping Methods. Review the database table sales_shipment or check the admin panel for shipping method optionsAffected if Shipment methods are actively configured or the shipment module is enabled in the Magento installation
You are affected if your Magento 2 version is below 2.1.18, 2.2.9, or 2.3.2 AND an authenticated administrator can access the shipment configuration settings in the admin panel.
Generated from the published advisory. Verify against your own configuration.
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 data2.1.182.2.92.3.2
Apply the appropriate Magento security patch or upgrade to version 2.1.18, 2.2.9, or 2.3.2 or later. Additionally, restrict administrator access to only trusted personnel and implement network segmentation to limit the impact of SSRF exploitation.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7892 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-7892 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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