CVE-2026-31887
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 · uneditedShopware is an open commerce platform. Prior to 6.7.8.1 and 6.6.10.15, an insufficient check on the filter types for unauthenticated customers allows access to orders of other customers. This is part of the deepLinkCode support on the store-api.order endpoint. This vulnerability is fixed in 6.7.8.1 and 6.6.10.15.
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 IDOR (Insecure Direct Object Reference) vulnerability in Shopware's store-api.order endpoint. The deepLinkCode filter mechanism lacks proper authorization validation, allowing unauthenticated customers to access other customers' orders by manipulating filter parameters.
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< 6.6.10.15>= 6.7.0.0, < 6.7.8.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/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 Shopware versionCheck the shopware version file (composer.json or a version info file in the Shopware installation directory) or query the Shopware health endpoint if availableAffected if The installed version is less than 6.6.10.15, or is 6.7.0.0 through 6.7.8.0 (including 6.7.0.0 and 6.7.8.0)
-
Confirm store-api endpoint exposureVerify that the /store-api/order endpoint is accessible without authentication by attempting a request to itAffected if The endpoint is publicly accessible without authentication (which is the default configuration)
-
Test deepLinkCode filter parameter manipulationMake an authenticated request to obtain a valid order with a known deepLinkCode, then attempt to access that same order using the deepLinkCode parameter from an unauthenticated request, or substitute another customer's deepLinkCode valueAffected if An unauthenticated request with a deepLinkCode parameter returns order details belonging to a different customer than the one making the request
A user is affected if their Shopware installation version falls within the vulnerable ranges AND the store-api.order endpoint is accessible without authentication, allowing unauthorized access to other customers' orders via the deepLinkCode parameter.
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.
dbcve · scoped6.6.10.156.7.8.1
Upgrade Shopware to version 6.7.8.1 or 6.6.10.15 or later to receive the patch. The fix adds proper validation to ensure filter parameters cannot be used to access orders belonging to other customers.
Upgrade to Shopware 6.6.10.15 (for 6.6.x branch) or 6.7.8.1 (for 6.7.x branch)
- Identify the current Shopware version by checking composer.json or the Shopware administration panel
- For Shopware 6.6.x versions (< 6.6.10.15): Plan upgrade to version 6.6.10.15 or later
- For Shopware 6.7.x versions (>= 6.7.0.0 and < 6.7.8.1): Plan upgrade to version 6.7.8.1 or later
- Execute the upgrade using Composer: composer require shopware/core:^6.6.10.15 or composer require shopware/core:^6.7.8.1 as appropriate for your branch
- Run Shopware database migrations: bin/console database:migrate
- Clear the Shopware cache: bin/console cache:clear
- Verify the new version in the administration panel
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.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,992.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31887 — 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-2026-31887 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