Shopware has user enumeration via distinct error codes on Store API login endpoint
shopware core · shopware platform
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| shopware/platform Packagist |
|
|
| shopware/core Packagist |
|
shopware core · shopware platform
| Product | Affected | Fixed in |
|---|---|---|
| shopware/platform Packagist |
|
|
| shopware/core Packagist |
|
|
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.
From the CVE record · GitHub_M
The Shopware Store API login endpoint returns different errors for registered and unknown customer email addresses, and echoes unknown addresses. An unauthenticated attacker can use these responses to enumerate customer accounts remotely without user interaction.
Operators using affected Packagist shopware/platform or shopware/core releases, including versions before the applicable 6.6.10.x fix and 6.7.0.0 through 6.7.8.0, should check their installations.