Shopware has user enumeration via distinct error codes on Store API login endpoint
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 6.7.8.1, 6.6.10.15, 6.6.10.14
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
Shopware 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.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- shopware core
From 6.7.0.0 · fixed in 6.7.8.1; fixed in 6.6.10.15
- shopware platform
From 6.7.0.0 · fixed in 6.7.8.1; fixed in 6.6.10.14
- shopware/platformPackagist
From 6.7.0.0 · fixed in 6.7.8.1
- shopware/platformPackagist
fixed in 6.6.10.14
- shopware/corePackagist
From 6.7.0.0 · fixed in 6.7.8.1
- shopware/corePackagist
fixed in 6.6.10.15