CVE-2019-8235
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 Magento 2.3 prior to 2.3.1, 2.2 prior to 2.2.8, and 2.1 prior to 2.1.17 versions. An authenticated user may be able to view personally identifiable shipping details of another user due to insufficient validation of user controlled input.
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 · moderate confidenceThis is an IDOR (Insecure Direct Object Reference) vulnerability in Magento where an authenticated user can view shipping PII (personally identifiable information) of other customers by manipulating object references (likely order IDs or customer IDs) in requests. The root cause is insufficient validation of user-controlled input, allowing unauthorized access to sensitive shipping data belonging to other users.
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.17>= 2.2.0, < 2.2.8>= 2.3.0, < 2.3.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Determine installed Magento versionRun the command 'php bin/magento --version' from the Magento root directory, or check the file 'app/etc/app.xml' for the version tag, or look at the composer.json file in the root directory.Affected if The installed version falls within >= 2.1.0 and < 2.1.17, OR >= 2.2.0 and < 2.2.8, OR >= 2.3.0 and < 2.3.1
-
Verify customer authentication is enabledConfirm that the Magento customer account functionality is active and customers can log in. Check if the module 'Magento_Customer' is enabled by running 'php bin/magento module:status Magento_Customer'.Affected if Customer authentication is enabled and the installed version is in the affected ranges listed above
-
Identify shipping information endpointsReview the API endpoints or web routes that handle shipping address retrieval. Look for endpoints under 'shipping-info' or similar paths in the 'webapi.xml' files within the Magento installation, typically in app/code/Magento/Checkout/etc/webapi.xml or related modules.Affected if Endpoints exist that return shipping address or shipping PII data to authenticated users
-
Test for IDOR on order/shipping retrievalLog in as a test customer account, then attempt to access order or shipping information using a different customer's order ID or object reference via the API or frontend. Observe whether the system returns data belonging to another customer without proper authorization errors.Affected if An authenticated user can retrieve shipping PII (name, address, phone, email) of other customers by manipulating order IDs or customer IDs in requests
If the installed Magento version is 2.1.0 through 2.1.16, 2.2.0 through 2.2.7, or 2.3.0, and customer accounts are active, the environment is likely affected by this IDOR vulnerability allowing unauthorized access to shipping information.
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.172.2.82.3.1
Apply the official Magento security patches (SUPEE-11219) or upgrade to Magento version 2.3.1, 2.2.8, or 2.1.17 which contain proper authorization checks to validate user access permissions before returning shipping details.
- Consultation3.0 h
- Implementation6.0 h
- Testing8.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 $5,472.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-8235 — 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-8235 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