CVE-2019-8145
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 inject arbitrary JavaScript code into the attribute set name when listing the products.
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 prior to 2.2.10 and 2.3 prior to 2.3.3 or 2.3.2-p1 allows an authenticated user to inject arbitrary JavaScript code into the attribute set name field. This malicious payload is stored in the database and executes when other users view product listings.
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.
-
Determine installed Magento versionRun command: php bin/magento --version or check composer.json for the magento/product-community-edition versionAffected if Version falls within >= 2.2.0, < 2.2.10 OR >= 2.3.0, < 2.3.2-p1 OR = 2.3.2 (the system is in the affected range)
-
Verify admin access existsConfirm whether any user accounts have access to the Magento admin panel with privileges to manage attribute sets under Stores > Attributes > Attribute SetAffected if An authenticated admin user exists with access to create or edit attribute sets (required for injecting the malicious payload)
-
Inspect database for suspicious attribute set namesQuery the eav_attribute_set table in the Magento database: SELECT attribute_set_id, attribute_set_name, entity_type_id FROM eav_attribute_set WHERE attribute_set_name LIKE '%<script%' OR attribute_set_name LIKE '%javascript:%' OR attribute_set_name LIKE '%onload=%'Affected if Any attribute set records contain HTML script tags, javascript: protocols, or event handler attributes like onload in the name field
The environment is affected if Magento version is in the vulnerable range AND an attacker with admin access could inject a malicious attribute set name, or if the database already contains XSS payloads in the eav_attribute_set table.
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, 2.3.2-p1, or 2.3.3 or later to remediate the vulnerability. Alternatively, implement input validation and output encoding on the attribute set name parameter.
- Consultation3.0 h
- Implementation6.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8145 — 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-8145 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