Shopware default newsletter opt-in settings allow for mass sign-up abuse
Published 9 Apr 2025 · Updated 10 Sept 2025
Affected packages
- Affected
- >=6.6.0.0-rc1 <6.6.10.3
- Fixed in
- 6.6.10.3
composer require shopware/core:^6.6.10.3- Affected
- >=6.6.0.0-rc1 <6.6.10.3
- Fixed in
- 6.6.10.3
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
composer require shopware/platform:^6.7.0.0-rc2- Affected
- >=6.7.0.0-rc1 <6.7.0.0-rc2
- Fixed in
- 6.7.0.0-rc2
composer require shopware/core:^6.7.0.0-rc2- Affected
- <6.5.8.17
- Fixed in
- 6.5.8.17
composer require shopware/core:^6.5.8.17- Affected
- <6.5.8.17
- Fixed in
- 6.5.8.17
composer require shopware/platform:^6.5.8.17Details
Impact
Currently the default settings for double-opt-in allow for mass unsolicited newsletter sign-ups without confirmation.
Default settings are:
Newsletter: Double Opt-in - active
Newsletter: Double opt-in for registered customers - disabled
Log-in & sign-up: Double opt-in on sign-up - disabled
With these settings, anyone can register an account on the shop using any e-mail-address and then check the check-box in the account page to sign up for the newsletter. The recipient will receive two mails confirming registering and signing up for the newsletter, no confirmation link needed to be clicked for either. In the backend the recipient is set to “instantly active”.
Patches
Update to Shopware 6.6.10.3 or 6.5.8.17
Workarounds
For older versions of 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-4h9w-7vfp-px8m 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.