CVE-2019-7890
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 · uneditedAn Insecure Direct Object Reference (IDOR) vulnerability exists in the order processing workflow 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 can lead to unauthorized access to order details.
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 confidenceThis is an Insecure Direct Object Reference (IDOR) vulnerability in Magento 2's order processing workflow. The application fails to properly validate that the requesting user has authorization to access specific order records, allowing an attacker to potentially view order details by manipulating order IDs in requests.
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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 2 installed versionRun 'bin/magento --version' from the Magento root directory, or inspect the composer.json file for the 'magento/product-community-edition' or 'magento/product-enterprise-edition' version entry, or view the version displayed in the admin panel footer.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.
-
Verify order API endpoint accessibilityConfirm that the Magento 2 REST API or frontend order viewing endpoints are accessible. Log in as a low-privileged user (such as a customer account) and attempt to access an order belonging to a different user by modifying the order ID parameter in the API request or URL.Affected if The system returns order details for an order ID that does not belong to the authenticated user, indicating missing authorization checks.
-
Review order access control configurationInspect the Magento admin panel under Stores > Configuration > Sales > Checkout and verify the settings for 'Allow Guests to Checkout' and customer account creation. Additionally, check the API role permissions for the customer account types in System > Permissions > User Roles.Affected if Customer accounts can access order processing endpoints without proper ownership validation, or API tokens for customer users are not scoped to their own orders.
The environment is affected if the Magento 2 version is 2.1.0-2.1.17, 2.2.0-2.2.8, or 2.3.0-2.3.1 AND order details from other users can be retrieved by manipulating order IDs in 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 data2.1.182.2.92.3.2
Apply the appropriate Magento 2 security patch or upgrade to version 2.1.18, 2.2.9, or 2.3.2 or later to include proper authorization checks in the order processing workflow.
- Consultation3.0 h
- Implementation4.0 h
- Testing4.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,648.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-7890 — 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-7890 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