# CVE-2022-24745: Guest session is shared between customers in shopware

> Guest sessions are shared between customers when HTTP cache is enabled, potentially exposing user data or allowing session hijacking.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Mar 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-jp6h-mxhx-pgqh

## What is CVE-2022-24745?

CVE-2022-24745 is a medium-severity authentication bypass vulnerability in Shopware Shopware, published on 9 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Shopware is an open commerce platform based on the Symfony php Framework and the Vue javascript framework. In affected versions guest sessions are shared between customers when HTTP cache is enabled. This can lead to inconsistent experiences for guest users. Setups with Varnish are not affected by this issue. This issue has been resolved in version 6.4.8.2. Users unable to upgrade should disable the HTTP Cache.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2022-24745?

4 open source packages ship an affected version, including shopware/platform and shopware/storefront. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `shopware/platform` | Packagist | All versions | 6.4.8.2 |
| `shopware/platform` | Packagist | All versions | 6.4.8.2 |
| `shopware/storefront` | Packagist | All versions | 6.4.8.2 |
| `shopware/storefront` | Packagist | All versions | 6.4.8.2 |

Products: Shopware Shopware.

## How do I fix CVE-2022-24745?

Upgrade shopware/platform to 6.4.8.2 or later.

## Is CVE-2022-24745 being exploited?

There is no known exploitation of CVE-2022-24745 in the wild and no public exploit code.

## Other vulnerabilities in Shopware Shopware

- [CVE-2023-22731](https://insights.sbomify.com/CVE-2023-22731/): Improper Control of Generation of Code in Twig rendered views in shopware (critical 10.0)
- [CVE-2016-3109](https://insights.sbomify.com/CVE-2016-3109/): Shopware RCE Vulnerability (critical 9.8)
- [CVE-2024-22406](https://insights.sbomify.com/CVE-2024-22406/): Blind SQL-injection in DAL aggregations in Shopware (critical 9.3)
- [CVE-2021-32711](https://insights.sbomify.com/CVE-2021-32711/): Leak of information via Store-API (critical 9.1)
- [CVE-2026-31887](https://insights.sbomify.com/CVE-2026-31887/): Shopware unauthenticated data extraction possible through store-api.order endpoint (high 8.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-24745 and fix it if it is affected.

What it is: CVE-2022-24745 is a medium-severity authentication bypass vulnerability in Shopware Shopware, published on 9 Mar 2022. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-24745 in the wild and no public exploit code.

Affected packages and fixed versions:
- shopware/platform (Packagist): affected all versions; fixed in 6.4.8.2
- shopware/platform (Packagist): affected all versions; fixed in 6.4.8.2
- shopware/storefront (Packagist): affected all versions; fixed in 6.4.8.2
- shopware/storefront (Packagist): affected all versions; fixed in 6.4.8.2

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2022-24745/ (Markdown: https://insights.sbomify.com/CVE-2022-24745/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2022-24745
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2022-24745
- OSV: https://osv.dev/vulnerability/CVE-2022-24745

---
From sbomify Insights: https://insights.sbomify.com/CVE-2022-24745/
Summaries are generated and may contain mistakes; the official description above is the record.