CVE-2019-7882
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 WYSIWYG editor of 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 privileges to the editor can inject malicious SWF files.
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 vulnerability exists in the WYSIWYG editor of Magento Open Source and Commerce versions prior to 2.3.2/2.2.9/2.1.18 (and 1.x prior to 1.9.4.2/1.14.4.2). Authenticated users with privileges to the editor can inject malicious SWF (Shockwave Flash) files that execute arbitrary JavaScript when viewed by other users, leading to session hijacking or other client-side attacks.
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
- 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.
-
Determine installed Magento versionCheck the version.php file in app/Mage.php (1.x) or composer.json in the Magento root directory (2.x) for the exact version numberAffected if The installed version falls within any of these ranges: < 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 WYSIWYG editor is enabledFor Magento 2.x, navigate to Content > Configuration > WYSIWYG Options or check core_config_data for path 'cms/wysiwyg/enabled'. For 1.x, check System > Configuration > Content Management > WYSIWYG EditorAffected if WYSIWYG editor is set to Enabled (any option other than Disabled)
-
Check user role permissions for editor accessNavigate to System > Permissions > User Roles (Magento 1.x) or System > Permissions > User Roles (Magento 2.x) and review which roles have access to Content > Pages, Content > Blocks, or Catalog > Categories where the editor is usedAffected if Any user role has privileges to use the WYSIWYG editor in CMS pages, blocks, or category descriptions
-
Search for SWF file uploads in media directoriesUse file system search to find .swf files in media/wysiwyg/, media/editor/, or pub/media/ directories. In database, query cms_page and cms_block tables for any content containing '.swf' stringsAffected if Any .swf files exist in WYSIWYG-related media directories or SWF references are found in CMS content tables
-
Review recent CMS content changes for suspicious embedded contentCheck cms_page_history and cms_block_history tables (if available) or review recent edits to pages and blocks for base64-encoded content, object/embed tags, or unusual media referencesAffected if CMS content contains suspicious Flash object embeddings, encoded scripts, or unexpected media file references that could contain malicious payloads
The environment is affected if the installed Magento version is within the vulnerable ranges AND the WYSIWYG editor is enabled with any non-admin user having access to it.
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+/1.14.4.2+ (1.x) or 2.1.18+/2.2.9+/2.3.2+ (2.x). Additionally, restrict WYSIWYG editor privileges to minimal trusted users and implement Content Security Policy headers to mitigate XSS risks.
- Consultation1.0 h
- Implementation3.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7882 — 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-7882 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