CVE-2019-7899
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 · uneditedNames of disabled downloadable products could be disclosed due to inadequate validation of user input in 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.
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 confidenceMagento does not properly validate user input when handling requests for downloadable products, allowing unauthenticated attackers to discover the names of disabled downloadable products. This information disclosure occurs because the application processes requests for disabled products without adequate access control checks.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check Magento versionFor Magento 1.x: check app/Mage.php for Mage::getVersion() or log into admin panel and check footer. For Magento 2.x: run 'bin/magento --version' or check composer.jsonAffected if Version is < 1.9.4.2 or < 1.14.4.2 (Magento 1.x); or >= 2.1.0 and < 2.1.18, >= 2.2.0 and < 2.2.9, or >= 2.3.0 and < 2.3.2 (Magento 2.x)
-
Verify downloadable product feature is in useCheck if downloadable products are configured: in Magento admin go to Catalog > Products and filter by 'Downloadable' product type, or query the catalog_product_entity table for entity_type_id corresponding to downloadable productsAffected if Downloadable products exist in the catalog and the feature is enabled
-
Identify disabled downloadable productsIn Magento admin, filter downloadable products by status 'Disabled', or query the database: SELECT * FROM catalog_product_entity_int WHERE attribute_id = (SELECT attribute_id FROM eav_attribute WHERE attribute_code = 'status' AND entity_type_id = [downloadable_type_id]) AND value = 2Affected if There are downloadable products with status disabled in the system
-
Test URL enumeration of disabled downloadable productsAttempt to access a known disabled downloadable product directly via its URL pattern (typically /downloadable/download/link/id/[product_id] or /catalog/product/view/id/[product_id]/) without authenticationAffected if The disabled downloadable product is accessible and reveals product name or download links to unauthenticated users
The environment is affected if the Magento version falls within the vulnerable ranges AND downloadable products exist AND disabled downloadable products can be enumerated or accessed by unauthenticated users via direct URL requests.
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
Apply the official Magento security patches (SUPEE-10888 for Magento 1.x and MDVA-xxxxx for Magento 2.x) or upgrade to the fixed versions (Magento 1.9.4.2+, 1.14.4.2+, 2.1.18+, 2.2.9+, 2.3.2+). Verify that disabled downloadable products are no longer accessible via direct URL enumeration.
- 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-7899 — 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-7899 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