CVE-2019-7921
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 vulnerability exists in the product catalog form of 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 could be exploited by an authenticated user with privileges to the product catalog to inject malicious javascript.
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 exists in the product catalog form of Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, and Magento 2.3 prior to 2.3.2. An authenticated user with privileges to access the product catalog can inject malicious JavaScript into form fields, which will be stored and executed when other users view the affected content.
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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/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.
-
Identify installed Magento versionRun 'php bin/magento --version' from the Magento root directory or inspect the composer.json file for the 'version' fieldAffected if The version displayed is 2.1.0 to 2.1.17, 2.2.0 to 2.2.8, or 2.3.0 to 2.3.1 (falls within < 2.1.18, < 2.2.9, or < 2.3.2)
-
Verify product catalog module is enabledCheck if the Magento Catalog module is installed and enabled by reviewing the app/etc/config.php file or running 'php bin/magento module:status' to list active modulesAffected if The Catalog module (Magento_Catalog) is listed as enabled or active
-
Confirm admin user access to product catalog formReview user roles and permissions in the Magento admin panel under System > Permissions > User Roles, or query the authorization_rule table in the Magento database for catalog-related privilegesAffected if Any authenticated admin user has privileges to access or edit the product catalog form (privileges to access Catalog > Products)
-
Inspect product catalog form fields for input validationExamine the product edit form in the Magento admin panel (Catalog > Products > Edit any product) and check if HTML/script tags can be submitted in fields such as product name, description, or meta fields without being sanitizedAffected if JavaScript tags such as <script>alert('XSS')</script> can be submitted and are stored without sanitization when saving a product
You are affected if your Magento version is within the affected ranges AND the product catalog module is accessible to authenticated users who can inject unsanitized script content into form 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.1.182.2.92.3.2
Apply the Magento security patch or upgrade to Magento 2.1.18, 2.2.9, or 2.3.2 or later. Input validation and output encoding should also be implemented on form fields in the product catalog.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.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,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7921 — 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-7921 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