CVE-2019-7858
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 cryptographic flaw in 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 resulted in storage of sensitive information with an algorithm that is insufficiently resistant to brute force attacks.
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 cryptographic flaw in 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 resulted in sensitive information being stored using an encryption algorithm with insufficient resistance to brute force attacks, potentially exposing stored credentials or other sensitive data to offline cryptographic 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>= 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 Magento installation versionRun the CLI command 'php bin/magento --version' from the Magento root directory, or check the composer.json file for the 'version' field under 'require' for 'magento/product-community-edition' or 'magento/enterprise-edition'Affected if The version shown is between 2.1.0 and 2.1.17, between 2.2.0 and 2.2.8, or between 2.3.0 and 2.3.1
-
Confirm version source is Magento Commerce or Open SourceCheck if the installation is Magento Open Source (formerly Community Edition) or Magento Commerce (formerly Enterprise Edition) by reviewing the composer.json 'name' field or the admin panel footer for the edition typeAffected if The instance is any edition running a version in the affected ranges listed above
-
Verify presence of sensitive encrypted dataReview the database for any stored credentials, API keys, payment tokens, or other sensitive data that may have been encrypted using Magento's encryption framework. This data would have been encrypted during normal Magento operations prior to the patchAffected if Sensitive data exists in the database that was encrypted by versions in the affected range, making it vulnerable to offline brute force attacks
You are affected if your Magento installation runs any version between 2.1.0 and 2.1.17, 2.2.0 and 2.2.8, or 2.3.0 and 2.3.1, and you have sensitive data in the database that was encrypted using the vulnerable cryptographic implementation.
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 Magento to version 2.1.18 or later, 2.2.9 or later, or 2.3.2 or later to apply the corrected cryptographic implementation.
- Consultation2.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,520.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7858 — 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-7858 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