# GHSA-r9vc-jfmh-6j48: TYPO3 frontend login vulnerable to Session Fixation

> Attackers can hijack user sessions by fixing session IDs before authentication, potentially gaining unauthorized access to authenticated accounts.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 May 2024

## What is GHSA-r9vc-jfmh-6j48?

GHSA-r9vc-jfmh-6j48 is an authentication bypass vulnerability in typo3/cms, published on 30 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

It has been discovered that TYPO3 is susceptible to session fixation. If a user authenticates while anonymous session data is present, the session id is not changed. This makes it possible for attackers to generate a valid session id, trick users into using this session id (e.g. by leveraging a different Cross-Site Scripting vulnerability) and then maybe getting access to an authenticated session.

## Which versions are affected by GHSA-r9vc-jfmh-6j48?

4 open source packages ship an affected version, including typo3/cms.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.14 |
| `typo3/cms` | Packagist | From 6.2.0 | 6.2.14 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.3.1 |
| `typo3/cms` | Packagist | From 7.0.0 | 7.3.1 |

## How do I fix GHSA-r9vc-jfmh-6j48?

Upgrade typo3/cms to a fixed version for your release line: 6.2.14 or 7.3.1.

## Is GHSA-r9vc-jfmh-6j48 being exploited?

There is no known exploitation of GHSA-r9vc-jfmh-6j48 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-r9vc-jfmh-6j48 and fix it if it is affected.

What it is: GHSA-r9vc-jfmh-6j48 is an authentication bypass vulnerability in typo3/cms, published on 30 May 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-r9vc-jfmh-6j48 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.14
- typo3/cms (Packagist): affected from 6.2.0; fixed in 6.2.14
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.3.1
- typo3/cms (Packagist): affected from 7.0.0; fixed in 7.3.1

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/GHSA-r9vc-jfmh-6j48/ (Markdown: https://insights.sbomify.com/GHSA-r9vc-jfmh-6j48/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-r9vc-jfmh-6j48

---
From sbomify Insights: https://insights.sbomify.com/GHSA-r9vc-jfmh-6j48/
Summaries are generated and may contain mistakes; the official description above is the record.