CVE-2019-7923
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 server-side request forgery (SSRF) 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. This can be exploited by authenticated user with admin privileges to manipulate shipment settings to execute arbitrary code.
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 a server-side request forgery (SSRF) vulnerability in Magento 2 e-commerce platforms (versions 2.1 prior to 2.1.18, 2.2 prior to 2.2.9, and 2.3 prior to 2.3.2). The flaw allows an authenticated administrator to manipulate shipment settings in a way that causes the server to make arbitrary HTTP requests to attacker-controlled endpoints, potentially leading to remote code execution.
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 versionRun the command: php bin/magento --version or check the file app/etc/env.php for the version entry, or view composer.json for the magento/product-community-edition versionAffected if The version falls within 2.1.0 to <2.1.18, 2.2.0 to <2.2.9, or 2.3.0 to <2.3.2
-
Verify admin panel accessibilityCheck if the /admin or custom admin URL path is publicly accessible by reviewing web server configuration (e.g., nginx.conf, .htaccess, or Apache virtual host settings)Affected if The admin panel is exposed to untrusted networks or the internet
-
Identify shipment configuration endpointInspect the admin panel under Stores > Configuration > Sales > Shipping Methods or check the database table core_config_data for paths containing 'shipping' and 'method'Affected if Shipment methods configuration is present and modifiable by an authenticated admin
-
Check for unusual outbound HTTP requestsReview web server access logs and application logs (var/log/exception.log, var/log/system.log) for suspicious outbound requests from the server to unknown external IPs or domainsAffected if Logs show outbound HTTP requests initiated by the Magento application to unexpected external endpoints
You are affected if your Magento 2 installation version is 2.1.0 to <2.1.18, 2.2.0 to <2.2.9, or 2.3.0 to <2.3.2 and the admin panel is accessible to an authenticated user who can modify shipment settings.
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 Magento 2.1.18, 2.2.9, 2.3.2 or later. Restrict admin panel access to trusted personnel and monitor for unusual shipment configuration changes.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7923 — 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-7923 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