MediumGHSA-hh7j-6x3q-f52hCVE-2025-30150

Shopware 6 allows attackers to check for registered accounts through the store-api

Published 8 Apr 2025 · Updated 10 Sept 2025

Affected packages

Affected
>=6.6.0.0 <6.6.10.3
Fixed in
6.6.10.3
Update to the fixed version for your release line, for example:composer require shopware/core:^6.6.10.3
Affected
>=6.6.0.0 <6.6.10.3
Fixed in
6.6.10.3
Update to the fixed version for your release line, for example:composer require shopware/platform:^6.6.10.3
Affected
>=6.7.0.0-rc1 <6.7.0.0-rc2
Fixed in
6.7.0.0-rc2
Update to the fixed version for your release line, for example:composer require shopware/core:^6.7.0.0-rc2
Affected
>=6.7.0.0-rc1 <6.7.0.0-rc2
Fixed in
6.7.0.0-rc2
Update to the fixed version for your release line, for example:composer require shopware/platform:^6.7.0.0-rc2
Affected
<6.5.8.18
Fixed in
6.5.8.18
Update to the fixed version for your release line, for example:composer require shopware/core:^6.5.8.18
Affected
<6.5.8.18
Fixed in
6.5.8.18
Update to the fixed version for your release line, for example:composer require shopware/platform:^6.5.8.18

Details

Impact

Through the store-api it is possible as a attacker to check if a specific e-mail address has an account in the shop.

Using the store-api endpoint /store-api/account/recovery-password you get the response

{"errors":[{"status":"404","code":"CHECKOUT__CUSTOMER_NOT_FOUND","title":"Not Found","detail":"No matching customer for the email \u0022asdasfd@asdads.de\u0022 was found.","meta":{"parameters":{"email":"asdasfd@asdads.de"}}}]}

which indicates clearly that there is no account for this customer. In contrast you get a success response if the account was found.

Patches

Update to Shopware 6.6.10.3

Workarounds

For older versions of 6.5 or 6.4, corresponding security measures are also available via a plugin. For the full range of functions, we recommend updating to the latest Shopware version.

Is GHSA-hh7j-6x3q-f52h in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected shopware/core, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.