SQL Injection Vulnerability in TYPO3 Backend History Module

typo3/cms Updated 02 Oct 2025

Summary

17/05/2022
Yes i
Moderate
Not published

CVE-2012-6144: Typo3 Backend History Module Vulnerable to SQL Injection. Affects typo3/cms across 3 version ranges.

>= 4.5.0, < 4.5.21 >= 4.6.0, < 4.6.14 >= 4.7.0, < 4.7.6

Fixed in 4.5.21, 4.6.14 or 4.7.6, 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 Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

Background

TYPO3 is an open-source content management system (CMS) written in PHP. It is widely used for building websites and web applications. The TYPO3 CMS includes a Backend History module that allows administrators to view and track changes made to the system. However, versions 4.5.x before 4.5.21, 4.6.x before 4.6.14, and 4.7.x before 4.7.6 are vulnerable to a SQL injection attack in the Backend History module. This vulnerability arises due to the lack of proper encoding of user input. Exploiting this vulnerability requires a valid backend login.

Vulnerability Detail

The SQL injection vulnerability in the TYPO3 Backend History module allows an attacker to manipulate SQL queries by injecting malicious code. This can lead to unauthorized access, data leakage, data manipulation, and even remote code execution. The lack of input encoding enables an attacker to craft malicious input that is executed as part of the SQL query. As a result, the attacker can bypass authentication, extract sensitive information, modify data, or execute arbitrary SQL commands.

How To Fix

Fixed versions by release line

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

  • >= 4.5.0, < 4.5.21 4.5.21
    composer require typo3/cms:4.5.21
  • >= 4.6.0, < 4.6.14 4.6.14
    composer require typo3/cms:4.6.14
  • >= 4.7.0, < 4.7.6 4.7.6
    composer require typo3/cms:4.7.6

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

Workaround

As a temporary workaround, TYPO3 administrators can disable or restrict access to the Backend History module for untrusted users. This can be done by modifying the access permissions or disabling the module entirely. However, this is not a permanent solution and upgrading to the latest patched version is strongly recommended.

Conclusion

The SQL injection vulnerability in the TYPO3 Backend History module can have serious security implications. It is crucial for TYPO3 users to upgrade to the latest patched version of the CMS to mitigate this vulnerability. For further assistance and support in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for typo3/cms →

Share this vulnerability

FAQ

TYPO3 is an open-source content management system (CMS) written in PHP. It is widely used for building websites and web applications.

The Backend History module in TYPO3 allows administrators to view and track changes made to the system. It provides a log of actions performed by users in the backend.

The SQL injection vulnerability in the Backend History module occurs due to the lack of proper encoding of user input. This allows an attacker to inject malicious SQL code and manipulate the SQL queries executed by the module.

The potential consequences of this vulnerability include unauthorized access to sensitive information, data leakage, data manipulation, and even remote code execution. An attacker can exploit this vulnerability to bypass authentication, extract sensitive data, modify data, or execute arbitrary SQL commands.

To fix this vulnerability, TYPO3 users should upgrade to the latest patched version of the CMS. Upgrading to version 4.5.21 or later (for TYPO3 4.5.x), version 4.6.14 or later (for TYPO3 4.6.x), or version 4.7.6 or later (for TYPO3 4.7.x) is recommended.

Related vulnerabilities

Recent vulnerabilities recorded for typo3/cms.

Sponsored Lume, the Habilume companion Habilume Habit tracker with a companion that grows with you Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent. App Store Google Play

How To Fix

Fixed versions by release line

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

  • >= 4.5.0, < 4.5.21 4.5.21
    composer require typo3/cms:4.5.21
  • >= 4.6.0, < 4.6.14 4.6.14
    composer require typo3/cms:4.6.14
  • >= 4.7.0, < 4.7.6 4.7.6
    composer require typo3/cms:4.7.6

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