Authentication Bypass in TYPO3 Frontend

typo3/cms Updated 02 Oct 2025

Summary

05/06/2024
MODERATE
Yes i
Moderate
5.4

GHSA-mh3r-6cp5-hc2j: Authentication Bypass in TYPO3 Frontend. Affects typo3/cms versions >= 8.2.0, < 8.6.1. Fixed in 8.6.1. 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 websites and web applications. It provides a robust set of features for managing content, user authentication, and frontend rendering. However, a vulnerability has been discovered in TYPO3 CMS that allows an attacker to bypass authentication restrictions in the frontend.

Vulnerability Detail

The vulnerability arises due to a late initialization of the TCA (Table Configuration Array) in TYPO3 CMS. This leads to the authentication service failing to properly restrict frontend users based on validation rules. As a result, it becomes possible for restricted frontend users, such as those with disabled accounts, to authenticate and gain unauthorized access to restricted resources.

How To Fix

Minimum fixed version

8.6.1

This is the first release that contains the fix.

composer require typo3/cms:8.6.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

If upgrading to the latest version is not immediately feasible, a temporary workaround can be implemented by modifying the authentication service code. The following code snippet demonstrates the workaround:

// Apply the workaround in the authentication service
// Add this code in the affected TYPO3 CMS version

if ($frontendUser->isDisabled()) {
    // Redirect or deny access
    // Example: Redirect to homepage
    $response->redirectTo('/');
}

Conclusion

The authentication bypass vulnerability in TYPO3 CMS frontend can lead to unauthorized access by restricted users. It is crucial to apply the recommended fix by upgrading to version 8.6.1 or a later version. If immediate upgrade is not feasible, the provided workaround can be implemented. For further support on 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 used for building websites and web applications. It provides a wide range of features for content management, user authentication, and frontend rendering.

The vulnerability occurs due to a late initialization of the TCA in TYPO3 CMS. This causes the authentication service to fail in properly restricting frontend users based on validation rules, allowing restricted users to authenticate and gain unauthorized access.

The impact of this vulnerability is that restricted frontend users, such as those with disabled accounts, can bypass authentication and gain unauthorized access to restricted resources. This can lead to unauthorized disclosure of sensitive information or unauthorized actions within the TYPO3 CMS frontend.

To fix this vulnerability, it is recommended to upgrade TYPO3 CMS to version 8.6.1 or any subsequent version that includes the fix. Upgrading will ensure that the TCA is initialized correctly and authentication restrictions are properly enforced.

Yes, if immediate upgrade is not possible, a temporary workaround can be implemented by modifying the authentication service code. The provided code snippet demonstrates the workaround.

References

Related vulnerabilities

Recent vulnerabilities recorded for typo3/cms.

How To Fix

Minimum fixed version

8.6.1

This is the first release that contains the fix.

composer require typo3/cms:8.6.1

Tip — Not sure which version your app runs? Vulert can match this fix to it. 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