CVE-2025-32378
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedShopware is an open source e-commerce software platform. Prior to 6.6.10.3 or 6.5.8.17, the default settings for double-opt-in allow for mass unsolicited newsletter sign-ups without confirmation. Default settings are Newsletter: Double Opt-in set to active, Newsletter: Double opt-in for registered customers set to disabled, and Log-in & sign-up: Double opt-in on sign-up set to 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”. This vulnerability is fixed in 6.6.10.3 or 6.5.8.17.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceShopware prior to 6.6.10.3 or 6.5.8.17 has insecure default double-opt-in settings for newsletter subscriptions. When Newsletter: Double Opt-in is active but 'Double opt-in for registered customers' and 'Double opt-in on sign-up' are disabled, registered users can subscribe to newsletters without clicking a confirmation link, resulting in instantly active subscriptions.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 6.5.8.17>= 6.6.0.0, < 6.6.10.3= 6.7.0.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check installed Shopware versionLocate the Shopware installation and identify the exact version number (typically in a composer.json file, changelog, or admin panel under Settings > Basic Information > Version)Affected if The installed version is less than 6.5.8.17, or between 6.6.0.0 and 6.6.10.2, or exactly 6.7.0.0
-
Verify Newsletter Double Opt-in is enabledCheck the Shopware admin configuration under Settings > Newsletter > Newsletter registration, or inspect the system_config database table for the config key 'core.newsletter.doubleOptIn' set to trueAffected if Newsletter Double Opt-in is active (enabled)
-
Check if Double opt-in for registered customers is disabledInspect the Shopware admin configuration under Settings > Newsletter > Newsletter registration, or query the system_config database table for the config key 'core.newsletter.doubleOptInRegistered' and verify it is set to false or is absentAffected if This setting is disabled or not explicitly set to true for registered customers
-
Check if Double opt-in on sign-up is disabledInspect the Shopware admin configuration under Settings > Newsletter > Newsletter registration, or query the system_config database table for the config key 'core.newsletter.doubleOptInOnSignup' and verify it is set to false or is absentAffected if This setting is disabled or not explicitly set to true on sign-up
You are affected if your Shopware version falls within the vulnerable ranges AND Newsletter Double Opt-in is enabled while BOTH 'Double opt-in for registered customers' and 'Double opt-in on sign-up' are disabled, allowing instant newsletter subscriptions without email confirmation for registered users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped6.5.8.176.6.10.3
Update Shopware to version 6.6.10.3 or 6.5.8.17, or explicitly enable 'Double opt-in for registered customers' and 'Double opt-in on sign-up' settings in the Shopware admin configuration.
6.5.8.17 or 6.6.10.3 (depending on your current branch)
- Upgrade Shopware to version 6.5.8.17 (if on 6.5.x branch)
- OR upgrade Shopware to version 6.6.10.3 (if on 6.6.x branch)
- After upgrading, verify the double-opt-in settings in the Shopware admin backend under 'Settings > Newsletter' to ensure they are configured correctly
- Confirm that 'Newsletter: Double Opt-in' is enabled and 'Newsletter: Double opt-in for registered customers' is properly configured to prevent unauthorized newsletter subscriptions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32378 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-32378 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data