CVE-2011-4628: Typo3 Authentication Bypass

typo3/cms Updated 02 Oct 2025

Summary

22/04/2022
Yes i
Critical
9.8

CVE-2011-4628: Typo3 Authentication Bypass. Affects typo3/cms across 3 version ranges.

< 4.3.12 >= 4.4.0, < 4.4.9 >= 4.5.0, < 4.5.4

Fixed in 4.3.12, 4.4.9 or 4.5.4, 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 Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

Typo3 is a popular content management system (CMS) used for building websites and web applications. It provides a wide range of features and functionalities for managing and publishing content. However, versions before 4.3.12, 4.4.x before 4.4.9, and 4.5.x before 4.5.4 are vulnerable to an authentication bypass issue in the backend. This vulnerability allows remote attackers to bypass authentication mechanisms through a crafted request.

Vulnerability Detail

The authentication bypass vulnerability in Typo3 allows attackers to gain unauthorized access to the backend of the CMS. By exploiting this vulnerability, an attacker can bypass the authentication mechanisms and gain administrative privileges. This can lead to various malicious activities, such as modifying content, stealing sensitive information, or even taking control of the entire website. The vulnerability is considered critical with a CVSS score of 9.8.

How To Fix

Fixed versions by release line

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

  • < 4.3.12 4.3.12
    composer require typo3/cms:4.3.12
  • >= 4.4.0, < 4.4.9 4.4.9
    composer require typo3/cms:4.4.9
  • >= 4.5.0, < 4.5.4 4.5.4
    composer require typo3/cms:4.5.4

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 crucial to apply the recommended fix by upgrading to the latest version of Typo3.

Conclusion

The Typo3 authentication bypass vulnerability is a critical issue that allows remote attackers to gain unauthorized access to the backend of the CMS. To mitigate this vulnerability, it is crucial to upgrade to the latest version of Typo3, which includes the necessary fixes. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for typo3/cms →

Share this vulnerability

FAQ

Typo3 is a content management system (CMS) used for building websites and web applications. It provides a wide range of features and functionalities for managing and publishing content.

An authentication bypass vulnerability allows attackers to bypass the authentication mechanisms of a system or application, gaining unauthorized access and potentially performing malicious activities.

This vulnerability can be exploited by sending a crafted request to the Typo3 backend, bypassing the authentication mechanisms and gaining administrative privileges.

The potential consequences of this vulnerability include unauthorized access to the backend, modification of content, theft of sensitive information, and complete control of the affected website.

Yes, the fix for this vulnerability is available in the latest versions of Typo3. It is recommended to upgrade to the fixed versions to patch the vulnerability.

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.

  • < 4.3.12 4.3.12
    composer require typo3/cms:4.3.12
  • >= 4.4.0, < 4.4.9 4.4.9
    composer require typo3/cms:4.4.9
  • >= 4.5.0, < 4.5.4 4.5.4
    composer require typo3/cms:4.5.4

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