CVE-2019-8132
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 stored cross-site scripting (XSS) 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 can craft malicious payload in the template Name field for Email template in the "Design Configuration" dashboard.
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 confidenceA stored cross-site scripting (XSS) vulnerability in Magento 2.2 and 2.3 allows authenticated users to inject malicious JavaScript through the template Name field in the Design Configuration dashboard's Email templates. The input is not properly sanitized before being stored and rendered, allowing script execution in the context of other users viewing the email template configuration.
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.2.0, < 2.2.10>= 2.3.0, < 2.3.2= 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check Magento versionRun command: php bin/magento --version or inspect the file app/etc/app.xml for the version entryAffected if Version is >= 2.2.0 and < 2.2.10, OR >= 2.3.0 and <= 2.3.2
-
Identify Design Configuration email templatesQuery the core_config_data table or inspect the file system under app/design/adminhtml for custom email template configurations that include template namesAffected if Any email templates exist in the Design Configuration section of the Magento admin
-
Inspect template Name fields for unsanitized contentReview email template names in the database table template (or similar email template storage tables) for presence of HTML script tags or JavaScript event handlersAffected if Any template Name field contains unescaped HTML/Script tags like <script> or javascript: URIs
-
Verify admin user access logsCheck admin_user_action_log or similar audit tables for activity related to Design Configuration email template creation/modificationAffected if Authenticated admin users have created or modified email templates in Design Configuration
You are affected if your Magento version is 2.2.0-2.2.9, 2.3.0-2.3.2 and you have email templates configured in the Design Configuration section that may contain unsanitized JavaScript in template Name fields.
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.2.102.3.2
Update Magento to version 2.2.10 or later (for 2.2.x) or 2.3.3/2.3.2-p1 or later (for 2.3.x). Alternatively, implement proper input validation and output encoding for the template Name field in the Design Configuration email template functionality.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8132 — 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-8132 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