How severe is GHSA-5297-wrrp-rcj7?

GHSA-5297-wrrp-rcj7 has a CVSS score of 5.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-5297-wrrp-rcj7?

GHSA-5297-wrrp-rcj7 affects the following packages: shopware/core (Packagist), shopware/platform (Packagist), shopware/core (Packagist), shopware/platform (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-5297-wrrp-rcj7?

Update shopware/core to 6.5.8.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5297-wrrp-rcj7 is resolved across your whole dependency graph.

How do I detect GHSA-5297-wrrp-rcj7 in my Packagist dependencies?

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.

How do I mitigate GHSA-5297-wrrp-rcj7 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is GHSA-5297-wrrp-rcj7 actively exploited in the wild?

No public exploit code has been indexed for GHSA-5297-wrrp-rcj7 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-5297-wrrp-rcj7?

GHSA-5297-wrrp-rcj7 has an EPSS (Exploit Prediction Scoring System) score of 0.5%, placing it in the 43th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-5297-wrrp-rcj7?

GHSA-5297-wrrp-rcj7 is classified as CWE-613 (CWE-613). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-5297-wrrp-rcj7 published, and has it been updated?

GHSA-5297-wrrp-rcj7 was published on April 8, 2024 and was last updated on September 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

Shopware Improper Session Handling in store-api account logoutGHSA-5297-wrrp-rcj7

MEDIUMFix: shopware/shopware@5cc84dd

GHSA-5297-wrrp-rcj7 is a medium-severity (CVSS 5.3) CWE-613 vulnerability in shopware/core. A fix is available for shopware/core — see the affected versions and patch details below.

Also known asCVE-2024-31447

Published

Apr 8, 2024

Updated

Sep 10, 2026

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

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-5297-wrrp-rcj7.

EPSS Exploitation Probability

via FIRST.org ↗

0.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs43th percentile — riskier than 43% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected

🐘shopware/core🐘shopware/platform🐘shopware/core🐘shopware/platform

Real-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

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`shopware/core`	≥ 6.3.5.0&&< 6.5.8.8	6.5.8.8`composer require shopware/core:^6.5.8.8`
🐘Packagist	`shopware/platform`	≥ 6.3.5.0&&< 6.5.8.8	6.5.8.8`composer require shopware/platform:^6.5.8.8`
🐘Packagist	`shopware/core`	≥ 6.6.0.0-rc1&&< 6.6.1.0	6.6.1.0`composer require shopware/core:^6.6.1.0`
🐘Packagist	`shopware/platform`	≥ 6.6.0.0-rc1&&< 6.6.1.0	6.6.1.0`composer require shopware/platform:^6.6.1.0`

Affected Products

1 product · 2 configurations

Application

shopwareshopware

≥ 6.6.0.0 && < 6.6.1.0

range

Detection & mitigation playbook

Open-source dependency

Detect
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.5.8.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-5297-wrrp-rcj7 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### Impact When a authentificated 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. ### Patches The problem has been fixed with Shopware 6.6.1.0 and 6.5.8.8. ### Workarounds When you are not able to update, you can install the latest version of the Shopware Security Plugin.