Session Fixation Vulnerability in TYPO3 CMS

typo3/cms Updated 02 Oct 2025

Summary

30/05/2024
HIGH
Yes i
High
7.1

GHSA-r9vc-jfmh-6j48: TYPO3 frontend login vulnerable to Session Fixation. Affects typo3/cms across 2 version ranges.

>= 6.2.0, < 6.2.14 >= 7.0.0, < 7.3.1

Fixed in 6.2.14 or 7.3.1, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Your last release was probably never penetration tested Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

TYPO3 CMS is an open-source content management system used for building and managing websites. It provides a wide range of features and functionalities, including frontend login for user authentication. However, a vulnerability has been discovered in the frontend login process that makes TYPO3 susceptible to session fixation attacks.

Vulnerability Detail

The session fixation vulnerability in TYPO3 occurs when a user authenticates while anonymous session data is present. In this scenario, the session ID is not changed, allowing attackers to generate a valid session ID and trick users into using it. This can be achieved by leveraging a different Cross-Site Scripting vulnerability. By exploiting this vulnerability, attackers may gain unauthorized access to authenticated sessions, potentially leading to unauthorized actions or data exposure.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 6.2.0, < 6.2.14 6.2.14
    composer require typo3/cms:6.2.14
  • >= 7.0.0, < 7.3.1 7.3.1
    composer require typo3/cms:7.3.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no specific workaround provided for this vulnerability. It is crucial to apply the recommended fix by updating TYPO3 CMS to the fixed versions mentioned above.

Conclusion

The session fixation vulnerability in TYPO3 CMS can potentially lead to unauthorized access to authenticated sessions, compromising the security and integrity of the affected websites. It is highly recommended to update TYPO3 CMS to the fixed versions mentioned above to mitigate this vulnerability. For further support and assistance in vulnerability remediation, you can reach out to DevNack.com.

See every vulnerability recorded for typo3/cms →

Share this vulnerability

FAQ

TYPO3 CMS is an open-source content management system used for building and managing websites. It offers a wide range of features and functionalities for website development and content administration.

Session fixation is a type of attack where an attacker tricks a user into using a predetermined session ID. By fixing the session ID, the attacker can gain unauthorized access to the user's session and potentially perform malicious actions.

In TYPO3 CMS, if a user authenticates while anonymous session data is present, the session ID is not changed. This allows attackers to generate a valid session ID and trick users into using it, potentially gaining unauthorized access to authenticated sessions.

The session fixation vulnerability in TYPO3 CMS can lead to unauthorized access to authenticated sessions. Attackers may be able to perform actions on behalf of the authenticated user, potentially compromising sensitive data or performing malicious activities.

To protect your TYPO3 CMS installation from session fixation attacks, it is crucial to update to the fixed versions mentioned in the 'how_to_fix' section. Additionally, regularly applying security updates and best practices for web application security can help mitigate the risk of session fixation and other vulnerabilities.

Related vulnerabilities

Recent vulnerabilities recorded for typo3/cms.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 6.2.0, < 6.2.14 6.2.14
    composer require typo3/cms:6.2.14
  • >= 7.0.0, < 7.3.1 7.3.1
    composer require typo3/cms:7.3.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback