CVE-2010-5100: TYPO3 CMS-Install Tool Cross-Site Scripting Vulnerability

typo3/cms-install Updated 02 Oct 2025

Summary

17/05/2022
Yes i
Low
Not published

CVE-2010-5100: TYPO3 Cross-Site Scripting vulnerability in the Install Tool. Affects typo3/cms-install across 3 version ranges.

>= 4.2.0, < 4.2.16 >= 4.3.0, < 4.3.9 >= 4.4.0, < 4.4.5

Fixed in 4.2.16, 4.3.9 or 4.4.5, 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 Penetration testing for web, API and mobile 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-Install Tool is a component of the TYPO3 content management system that allows users to install and configure TYPO3 on a web server. It provides a web-based interface for managing the installation process and performing various administrative tasks. The tool is written in PHP and is a critical part of the TYPO3 CMS ecosystem.

Vulnerability Detail

The TYPO3 CMS-Install Tool is affected by multiple cross-site scripting (XSS) vulnerabilities. These vulnerabilities allow remote authenticated users to inject arbitrary web script or HTML into the tool via unspecified vectors. An attacker could exploit these vulnerabilities to execute malicious code in the context of the affected user's browser, potentially leading to session hijacking, data theft, or other forms of web application compromise.

How To Fix

Fixed versions by release line

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

  • >= 4.2.0, < 4.2.16 4.2.16
    composer require typo3/cms-install:4.2.16
  • >= 4.3.0, < 4.3.9 4.3.9
    composer require typo3/cms-install:4.3.9
  • >= 4.4.0, < 4.4.5 4.4.5
    composer require typo3/cms-install:4.4.5

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 security patches as soon as possible to mitigate the risk of exploitation.

Conclusion

The TYPO3 CMS-Install Tool is affected by multiple cross-site scripting vulnerabilities that can be exploited by remote authenticated users. To mitigate the risk of exploitation, it is recommended to upgrade to the latest version of TYPO3 CMS-Install Tool (4.2.16, 4.3.9, or 4.4.5) and apply the necessary security patches. For further support on vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for typo3/cms-install →

Share this vulnerability

FAQ

These vulnerabilities allow remote authenticated users to execute arbitrary code in the context of the affected user's browser. This could lead to session hijacking, data theft, or other forms of web application compromise.

There are no known instances of these vulnerabilities being exploited in the wild. However, it is important to apply the security patches to prevent potential exploitation.

No, these vulnerabilities can only be exploited by remote authenticated users.

While these vulnerabilities could potentially lead to data theft or unauthorized access, there is no inherent risk of data loss or corruption.

Yes, you can use the Vulert Playground (https://vulert.com/scanner) to check if your TYPO3 installation is affected by this vulnerability. Simply upload your composer.lock file to the playground, and it will analyze your dependencies and alert you if any vulnerabilities are found.

Related vulnerabilities

Recent vulnerabilities recorded for typo3/cms-install.

How To Fix

Fixed versions by release line

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

  • >= 4.2.0, < 4.2.16 4.2.16
    composer require typo3/cms-install:4.2.16
  • >= 4.3.0, < 4.3.9 4.3.9
    composer require typo3/cms-install:4.3.9
  • >= 4.4.0, < 4.4.5 4.4.5
    composer require typo3/cms-install:4.4.5

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