CVE-2024-31447
MEDIUMCVE-2024-31447 is a medium-severity (CVSS 5.3) CWE-613 vulnerability in shopware/core. O3 Security confirms whether CVE-2024-31447 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Shopware has Improper Session Handling in store-api
Blast Radius
shopware/core🐘shopware/platform🐘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
Shopware 6 is an open commerce platform based on Symfony Framework and Vue. Starting in version 6.3.5.0 and prior to versions 6.6.1.0 and 6.5.8.8, when a authenticated request is made to POST /store-api/account/logout, the cart will be cleared, but the User won't be logged out. This affects only the direct store-api usage, as the PHP Storefront listens additionally on CustomerLogoutEvent and invalidates the session additionally. The problem has been fixed in Shopware 6.6.1.0 and 6.5.8.8. Those who are unable to update can install the latest version of the Shopware Security Plugin as a workaround.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | shopware/core | ≥ 6.3.5.0&&< 6.5.8.8 | 6.5.8.8 |
| 🐘Packagist | shopware/platform | ≥ 6.3.5.0&&< 6.5.8.8 | 6.5.8.8 |
| 🐘Packagist | shopware/core | ≥ 6.6.0.0-rc1&&< 6.6.1.0 | 6.6.1.0 |
| 🐘Packagist | shopware/platform | ≥ 6.6.0.0-rc1&&< 6.6.1.0 | 6.6.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for shopware/core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update shopware/core to 6.5.8.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2024-31447 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 pinpoints whether CVE-2024-31447 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2024-31447. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2024-31447 in your dependencies?
O3 detects CVE-2024-31447 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.