Path Traversal in TYPO3 Core

typo3/cms Updated 02 Oct 2025

Summary

22/02/2024
MODERATE
Yes i
Moderate
Not published

GHSA-gj48-w74w-8gvm: Path Traversal in TYPO3 Core. Affects typo3/cms across 3 version ranges.

>= 6.2.0, < 6.2.29 >= 7.6.0, < 7.6.13 >= 8.0.0, < 8.4.1

Fixed in 6.2.29, 7.6.13 or 8.4.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 MarkAI Find prospects already talking about the problem you solve AI watches the communities your customers use to find qualified prospects, then alerts you when a conversation is worth joining. See MarkAI

Background

TYPO3 CMS is an open-source content management system that allows users to create and manage websites. It provides a wide range of features and functionalities, including content editing, user management, and extensibility through plugins. However, a vulnerability has been discovered in the TYPO3 Core that could allow attackers to bypass directory traversal checks by providing an invalid UTF-8 encoding sequence.

Vulnerability Detail

The vulnerability in TYPO3 Core arises from a loose type check in an API method. By exploiting this flaw, attackers can manipulate the encoding sequence to bypass the directory traversal check. This could potentially lead to unauthorized access to sensitive files and directories on the server. The impact of this vulnerability can vary depending on the specific configuration and permissions of the affected TYPO3 installation.

How To Fix

Fixed versions by release line

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

  • >= 6.2.0, < 6.2.29 6.2.29
    composer require typo3/cms:6.2.29
  • >= 7.6.0, < 7.6.13 7.6.13
    composer require typo3/cms:7.6.13
  • >= 8.0.0, < 8.4.1 8.4.1
    composer require typo3/cms:8.4.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 known workaround for this vulnerability. It is recommended to apply the fix by updating TYPO3 CMS to a secure version.

Conclusion

The path traversal vulnerability in TYPO3 Core can potentially allow attackers to bypass directory traversal checks and gain unauthorized access to sensitive files and directories. It is essential to update TYPO3 CMS to a secure version to mitigate the risk of exploitation. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for typo3/cms →

Share this vulnerability

FAQ

TYPO3 CMS is an open-source content management system that allows users to create and manage websites. It provides a wide range of features and functionalities.

Directory traversal is a vulnerability that allows an attacker to access files and directories outside the intended scope of the application. In this case, the vulnerability in TYPO3 Core allows bypassing the directory traversal check.

The impact of this vulnerability can vary depending on the specific configuration and permissions of the affected TYPO3 installation. However, it could potentially lead to unauthorized access to sensitive files and directories on the server.

To fix this vulnerability, it is recommended to update TYPO3 CMS to a version that includes the fix. Refer to the 'how_to_fix' section for specific version information.

There is no known workaround for this vulnerability. It is crucial to apply the fix by updating TYPO3 CMS to a secure version.

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.29 6.2.29
    composer require typo3/cms:6.2.29
  • >= 7.6.0, < 7.6.13 7.6.13
    composer require typo3/cms:7.6.13
  • >= 8.0.0, < 8.4.1 8.4.1
    composer require typo3/cms:8.4.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