CVE-2019-7859
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 path traversal vulnerability in the WYSIWYG editor for Magento 2.1 prior to 2.1.18, Magento 2.2 prior to 2.2.9, Magento 2.3 prior to 2.3.2 could result in unauthorized access to uploaded images due to insufficient access control.
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 path traversal vulnerability exists in the WYSIWYG editor for Magento versions 2.1 prior to 2.1.18, 2.2 prior to 2.2.9, and 2.3 prior to 2.3.2. The vulnerability allows attackers to traverse directories and access uploaded images outside the intended directory due to insufficient access control validation on file paths.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 the CLI command 'php bin/magento --version' or check the composer.json file in the Magento root directory for the installed version.Affected if The installed version falls within 2.1.0 to 2.1.17, 2.2.0 to 2.2.8, or 2.3.0 to 2.3.1.
-
Confirm WYSIWYG editor is enabledLog into the Magento Admin panel and navigate to Stores > Configuration > General > Content Management > WYSIWYG Options, or check the core_config_data table for the 'cms/wysiwyg/enabled' configuration value.Affected if WYSIWYG editor is set to Enabled (any option other than 'Disabled').
-
Check for untrusted file upload capabilitiesVerify if the WYSIWYG editor allows image uploads in CMS pages, blocks, or product descriptions. Attempt to access the editor in the Admin panel under Content > Pages, Blocks, or Products.Affected if The WYSIWYG editor is accessible and allows image/file uploads to untrusted users.
-
Inspect web server access controlsReview the web server configuration (Apache .htaccess or Nginx configuration) and Magento admin URL access controls to determine if the WYSIWYG upload functionality is exposed to unauthenticated users.Affected if The WYSIWYG upload endpoints are accessible without authentication or from untrusted network locations.
You are affected if your Magento installation runs version 2.1.0-2.1.17, 2.2.0-2.2.8, or 2.3.0-2.3.1 AND the WYSIWYG editor is enabled and accessible to untrusted users.
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
Upgrade to Magento version 2.1.18, 2.2.9, 2.3.2 or later. Until patched, restrict administrative access to the WYSIWYG editor and consider network-level restrictions to minimize exposure.
- Consultation2.0 h
- Implementation4.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,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7859 — 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-7859 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