GHSA-4h9w-7vfp-px8m — shopware/core
MEDIUMGHSA-4h9w-7vfp-px8m is a medium-severity (CVSS 5.3) CWE-799 vulnerability in shopware/core. A fix is available for shopware/core — see the affected versions and patch details below.
Shopware default newsletter opt-in settings allow for mass sign-up abuse
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-4h9w-7vfp-px8m.
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
How urgent is this, really
GHSA-4h9w-7vfp-px8m plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
shopware/core🐘shopware/platform🐘shopware/platform🐘shopware/core🐘shopware/core🐘shopware/platformReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | shopware/core | ≥ 6.6.0.0-rc1&&< 6.6.10.3 | 6.6.10.3composer require shopware/core:^6.6.10.3 |
| 🐘Packagist | shopware/platform | ≥ 6.6.0.0-rc1&&< 6.6.10.3 | 6.6.10.3composer require shopware/platform:^6.6.10.3 |
| 🐘Packagist | shopware/platform | ≥ 6.7.0.0-rc1&&< 6.7.0.0-rc2 | 6.7.0.0-rc2composer require shopware/platform:^6.7.0.0-rc2 |
| 🐘Packagist | shopware/core | ≥ 6.7.0.0-rc1&&< 6.7.0.0-rc2 | 6.7.0.0-rc2composer require shopware/core:^6.7.0.0-rc2 |
| 🐘Packagist | shopware/core | all versions | 6.5.8.17composer require shopware/core:^6.5.8.17 |
| 🐘Packagist | shopware/platform | all versions | 6.5.8.17composer require shopware/platform:^6.5.8.17 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update shopware/core to 6.6.10.3 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4h9w-7vfp-px8m is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-4h9w-7vfp-px8m can be triaged on real exposure rather than presence alone.
Tailored to GHSA-4h9w-7vfp-px8m. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4h9w-7vfp-px8m in your dependencies?
O3 Security finds GHSA-4h9w-7vfp-px8m across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.