CVE-2026-31888
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, the Store API login endpoint (POST /store-api/account/login) returns different error codes depending on whether the submitted email address belongs to a registered customer (CHECKOUT__CUSTOMER_AUTH_BAD_CREDENTIALS) or is unknown (CHECKOUT__CUSTOMER_NOT_FOUND). The "not found" response also echoes the probed email address. This allows an unauthenticated attacker to enumerate valid customer accounts. The storefront login controller correctly unifies both error paths, but the Store API does not — indicating an inconsistent defense. 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 confidenceThe Shopware Store API login endpoint (POST /store-api/account/login) returns distinct error codes depending on whether a submitted email exists in the system—CHECKOUT__CUSTOMER_AUTH_BAD_CREDENTIALS for registered users with wrong passwords versus CHECKOUT__CUSTOMER_NOT_FOUND for unknown emails. The 'not found' response also echoes back the probed email address. This inconsistency between the Store API and the storefront login controller allows unauthenticated attackers to enumerate valid customer accounts.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/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.
-
Identify installed Shopware versionCheck the version.php file in the root directory or use the admin panel (Settings > System > Info) to determine the exact Shopware versionAffected if Version is < 6.6.10.15 OR (>= 6.7.0.0 AND < 6.7.8.1)
-
Verify Store API endpoint accessibilityConfirm the endpoint /store-api/account/login is accessible by sending a POST request to your Shopware instanceAffected if The endpoint responds to unauthenticated requests
-
Test enumeration with non-existent emailSend a POST request to /store-api/account/login with a random email that does not exist (e.g., {"email":"[email protected]","password":"wrongpassword"}) and capture the response code and messageAffected if Response contains CHECKOUT__CUSTOMER_NOT_FOUND error code OR echoes back the submitted email address
-
Test enumeration with existing email but wrong passwordSend a POST request to /store-api/account/login with a known registered email but incorrect password (e.g., {"email":"[email protected]","password":"wrongpassword"}) and capture the response code and messageAffected if Response contains CHECKOUT__CUSTOMER_AUTH_BAD_CREDENTIALS error code AND differs from the 'not found' response
-
Compare error response consistencyCompare the error codes and messages from steps 3 and 4 - they should be identical (unified) in a patched versionAffected if Different error codes are returned for non-existent accounts vs. existing accounts with wrong passwords, or if the email is echoed in the 'not found' response
You are affected if your Shopware version falls within the vulnerable range AND the Store API login endpoint returns distinct error codes (CHECKOUT__CUSTOMER_NOT_FOUND vs CHECKOUT__CUSTOMER_AUTH_BAD_CREDENTIALS) that allow account enumeration.
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, which implements unified error responses that do not disclose account existence.
Upgrade to Shopware 6.6.10.15 (if on 6.6.x) or 6.7.8.1 (if on 6.7.x)
- 1. Backup your Shopware database and files before proceeding with any upgrade
- 2. Identify your current Shopware version using the admin panel or bin/console about command
- 3. If you are on Shopware 6.6.x branch: Upgrade to version 6.6.10.15 or later
- 4. If you are on Shopware 6.7.x branch: Upgrade to version 6.7.8.1 or later
- 5. Run the database migration using bin/console database:migrate or bin/console setup:upgrade
- 6. Clear the cache using bin/console cache:clear
- 7. Verify the fix by attempting to login with both valid and invalid email addresses through the Store API - both should now return the same error code
- 8. Test that legitimate customer login still functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-31888 — 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-31888 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