CVE-2019-7932
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 Open Source prior to 1.9.4.2, and Magento Commerce prior to 1.14.4.2, 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 admin privileges to create sitemaps can execute arbitrary PHP code by creating a malicious sitemap file.
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 confidenceRemote code execution vulnerability in Magento's sitemap creation feature. An authenticated administrator can upload a malicious sitemap file containing arbitrary PHP code, which gets executed by the server.
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< 1.9.4.2< 1.14.4.2>= 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 Magento versionLocate the version file: for Magento 1.x check app/Mage.php for the version constant, or for Magento 2.x check composer.json and app/etc/config.php to identify the installed versionAffected if The installed version falls within < 1.9.4.2, < 1.14.4.2, >= 2.1.0 and < 2.1.18, >= 2.2.0 and < 2.2.9, or >= 2.3.0 and < 2.3.2
-
Verify sitemap module is enabledFor Magento 1.x, inspect the app/etc/modules/*.xml files for Mage_XmlConnect or core module status; for Magento 2.x, run bin/magento module:status or check app/etc/config.php for the Magento_Sitemap module entryAffected if The sitemap module (Magento_Sitemap for M2, or core sitemap for M1) is listed as enabled in the configuration
-
Confirm admin panel accessibilityAttempt to access the admin login URL (typically /admin or /backend) or inspect the admin configuration in app/etc/env.php for Magento 2 or app/etc/local.xml for Magento 1 to verify the admin path is configuredAffected if The admin panel is accessible via a known or predictable URL path and accepts authentication credentials
-
Check sitemap generation permissionsIf logged in as an administrator, navigate to the sitemap creation interface: for Magento 1.x go to Catalog > Google Sitemaps; for Magento 2.x go to Marketing > SEO & Search > Sitemaps, or inspect the admin_user and authorization_role tables to see if any admin user has access to sitemap-related ACL resourcesAffected if An authenticated admin user has ACL permissions to create or edit sitemaps through the admin panel
You are affected if your Magento version is in the vulnerable ranges listed AND the sitemap module is enabled AND an administrator account with sitemap creation permissions can access 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 data1.9.4.21.14.4.22.1.18
Upgrade Magento to version 1.9.4.2+ (Open Source), 1.14.4.2+ (Commerce), 2.1.18+, 2.2.9+, or 2.3.2+ respectively. Restrict admin sitemap creation permissions until patched.
- Consultation4.0 h
- Implementation8.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7932 — 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-7932 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