CVE-2025-30150: Shopware 6 allows attackers to check for registered accounts through the store-api
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 which indicates clearly that there is no account for this customer. In contrast you get a success response if the account was found.
Published Apr 8, 2025 · Updated Sep 10, 2025
Affected packages
shopware/core
- Ecosystem
- Composer (PHP)
- Affected
- = 6.7.0.0-rc1
- Fixed in
- 6.7.0.0-rc2
- Check
composer show shopware/core
shopware/platform
- Ecosystem
- Composer (PHP)
- Affected
- = 6.7.0.0-rc1
- Fixed in
- 6.7.0.0-rc2
- Check
composer show shopware/platform
shopware/core
- Ecosystem
- Composer (PHP)
- Affected
- >= 6.6.0.0, <= 6.6.10.2
- Fixed in
- 6.6.10.3
- Check
composer show shopware/core
shopware/platform
- Ecosystem
- Composer (PHP)
- Affected
- >= 6.6.0.0, <= 6.6.10.2
- Fixed in
- 6.6.10.3
- Check
composer show shopware/platform
shopware/core
- Ecosystem
- Composer (PHP)
- Affected
- <= 6.5.8.17
- Fixed in
- 6.5.8.18
- Check
composer show shopware/core
shopware/platform
- Ecosystem
- Composer (PHP)
- Affected
- <= 6.5.8.17
- Fixed in
- 6.5.8.18
- Check
composer show shopware/platform
Advisory details
From the GitHub Advisory Database (CC BY 4.0).
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 \[email protected]\u0022 was found.","meta":{"parameters":{"email":"[email protected]"}}}]}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.
Credited to niklaswolf.
References
- https://github.com/shopware/shopware/security/advisories/GHSA-hh7j-6x3q-f52h
- https://github.com/shopware/shopware/releases/tag/v6.5.8.17
- https://github.com/shopware/shopware/releases/tag/v6.6.10.3
- https://github.com/shopware/shopware/releases/tag/v6.7.0.0-rc2
- https://nvd.nist.gov/vuln/detail/CVE-2025-30150
- https://github.com/advisories/GHSA-hh7j-6x3q-f52h
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology
More Composer (PHP) vulnerabilities
All Composer (PHP) entriesCVE-2026-48008
Shopware: Privilege Escalation via Sync API Integration Admin Flag Bypass
medium6.5Jun 4, 2026CVE-2026-48009
Shopware: Admin Account Takeover via User Recovery Hash Exposure
medium6.8Jun 4, 2026CVE-2026-48010
Shopware: Privilege escalation: non-admin user with user:create ACL can create admin accounts
medium6.5Jun 4, 2026CVE-2026-48011
Shopware: Timing-attack on admin panel allowing enumeration of administrator usernames
low3.7Jun 4, 2026CVE-2026-48012
Shopware SSO referer trust leading to an arbitrary redirect target
medium4.3Jun 4, 2026CVE-2026-48013
Shopware: SSRF in Media External-Link Endpoint Bypasses IP Validation
medium4.1Jun 4, 2026
