CVE-2025-32378

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”.

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.

Currently the default settings for double-opt-in allow for mass unsolicited newsletter sign-ups without confirmation.

Default settings are:

CVE-2025-32378 has a CVSS score of 5.3 (Low). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (6.6.10.3, 6.7.0.0-rc2, 6.5.8.17); upgrading removes the vulnerable code path.

Kodem intelligence

Update to Shopware 6.6.10.3 or 6.5.8.17

1. What is CVE-2025-32378? CVE-2025-32378 is a low-severity security vulnerability in shopware/core (composer), affecting versions >= 6.6.0.0-rc1, < 6.6.10.3. It is fixed in 6.6.10.3, 6.7.0.0-rc2, 6.5.8.17.
2. How severe is CVE-2025-32378? CVE-2025-32378 has a CVSS score of 5.3 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-32378?
   • shopware/core (composer) (versions >= 6.6.0.0-rc1, < 6.6.10.3)
   • shopware/platform (composer) (versions >= 6.6.0.0-rc1, < 6.6.10.3)
4. Is there a fix for CVE-2025-32378? Yes. CVE-2025-32378 is fixed in 6.6.10.3, 6.7.0.0-rc2, 6.5.8.17. Upgrade to this version or later.
5. Is CVE-2025-32378 exploitable, and should I be worried? Whether CVE-2025-32378 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-32378 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-32378?
   • Upgrade shopware/core to 6.6.10.3 or later
   • Upgrade shopware/platform to 6.6.10.3 or later
   • Upgrade shopware/platform to 6.7.0.0-rc2 or later
   • Upgrade shopware/core to 6.7.0.0-rc2 or later
   • Upgrade shopware/core to 6.5.8.17 or later
   • Upgrade shopware/platform to 6.5.8.17 or later