Servers and applications
CVE-2026-31888
User enumeration via distinct error codes on Store API login endpoint
- Severity
- Medium 5.3
- Published
- 11 Mar 2026
- Last changed
- 17 Jun 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 6.6.10.14, 6.6.10.15, 6.7.8.1
- Exploit chance
- 0.3% in the next 30 daysHigher than 17% of CVEs. EPSS by FIRST, 19 Nov 2026
- Weakness
- Response discrepancy (CWE-204)
- Attack
- Over the network · No login needed · No user action needed
- Attacker can
- Read some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N- Also known as
- GHSA-gqc5-xv7m-gcjq
- Sources
- NVD, Project advisories (GitHub)
Description
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 (CHECKOUTCUSTOMER_AUTH_BAD_CREDENTIALS) or is unknown (CHECKOUTCUSTOMER_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.
The storefront login controller demonstrates that Shopware's developers are aware of this risk class. AuthController::login() catches both exceptions together and returns a generic error:
The Store API LoginRoute::login() does NOT catch these exceptions. They propagate to the global ErrorResponseFactory, which serializes the distinct error codes into the JSON response:
This inconsistency confirms the Store API exposure is an oversight, not a design decision.
Affected software
| Software | Affected versions |
|---|---|
ShopwareServers and applications · cpe:a:shopware:shopware |
|
ShopwareServers and applications · github:shopware/shopware |
|
About Shopware
open-source e-commerce platform
- Monthly downloads (Packagist)
- 291,680Packagist, 15 Nov 2026
- Total downloads (Packagist)
- 6,581,000Packagist, 15 Nov 2026
- GitHub stars
- 3,471GitHub, 15 Nov 2026
- Forks
- 1,226GitHub, 15 Nov 2026
- Latest release
- v6.7.16.0GitHub, 15 Nov 2026
- Released
- 2 Nov 2026GitHub
- License
- MIT LicenseWikidata
- Written in
- PHPWikidata
- First published on GitHub
- 3 May 2018GitHub
Release lines
| Release | Latest | Security fixes |
|---|---|---|
| 6.7 | 6.7.16.0 | Until 28 Feb 2028 |
| 6.6 | 6.6.10.31 | Until 28 Feb 2028 |
| 6.5 | 6.5.8.19 | Until 28 Feb 2027 |
| 5.7 | 5.7.20 | Ended 31 Jul 2024 |
| 6.4 | 6.4.20.2 | Ended 14 May 2025 |
| 6.3 | 6.3.5.4 | Ended |
From endoflife.date.
Vulnerabilities in Shopware
- In our list
- 123
- Published in the last 12 months
- 39
- Critical, last 12 months
- 6
- High, last 12 months
- 15
- Known exploited
- 0
- GHSA-23g6-m65m-5qcgMissing authorization permits unauthorized media uploadsMedium 4.3 18 Nov 2026
- GHSA-3q8x-6fc9-5428Insufficient media validation permits unauthorized file operationsHigh 7.7 18 Nov 2026
- GHSA-x6mg-frx2-6p8jInsufficient App package validation permits server file disclosureHigh 7.4 18 Nov 2026
- GHSA-59j5-8mv2-2fc5Insufficient Twig template isolation permits privilege escalationHigh 7.3 18 Nov 2026
- GHSA-fmvh-847r-3hmqStore API aggregation validation bypass exposes sensitive informationCritical 9.1 18 Nov 2026
- GHSA-4v2w-jpmg-wp82Insufficient API access control exposes sensitive informationHigh 7.5 18 Nov 2026
References
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-31888
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-31888
- GitHub Advisory Database https://github.com/advisories/GHSA-gqc5-xv7m-gcjq
- github.com https://github.com/shopware/shopware/security/advisories/GHSA-gqc5-xv7m-gcjq