CVE-2013-4321: TYPO3 CMS Remote Authenticated Arbitrary Code Execution Vulnerability
Summary
CVE-2013-4321: TYPO3 vulnerable to remote authenticated arbitrary code execution. Affects typo3/cms across 2 version ranges.
>= 6.0.0, < 6.0.9
>= 6.1.0, < 6.1.4
Fixed in 6.0.9 or 6.1.4, depending on the release line you run. How to fix ↓
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.
No signup required · Results in about 60 seconds
Background
TYPO3 is an open-source content management system (CMS) widely used for building and managing websites. It offers a robust framework for developers and editors, enabling them to create dynamic web applications with ease. However, certain versions of TYPO3 have been found to be vulnerable to security issues, particularly in its File Abstraction Layer (FAL), which handles file management and storage. This vulnerability allows authenticated users to execute arbitrary PHP code, posing significant risks to the integrity and security of the application.
Vulnerability Detail
The vulnerability in TYPO3 arises from the File Abstraction Layer (FAL) in versions 6.0.x before 6.0.9 and 6.1.x before 6.1.4. It allows remote authenticated editors to execute arbitrary PHP code by manipulating file extensions during the renaming process. This issue is particularly concerning as it stems from an incomplete fix for a previous vulnerability (CVE-2013-4250), which means that even users with legitimate access can exploit this flaw to execute malicious code, potentially leading to unauthorized access and data breaches.
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
>= 6.0.0, < 6.0.96.0.9composer require typo3/cms:6.0.9 -
>= 6.1.0, < 6.1.46.1.4composer require typo3/cms:6.1.4
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, restrict access to the file renaming functionality for authenticated users until the update can be applied. This can be done by modifying user permissions in the TYPO3 backend to limit access to file management features.
Conclusion
The TYPO3 vulnerability CVE-2013-4321 poses a significant risk to installations of the CMS, allowing authenticated users to execute arbitrary code. It is crucial to update to the latest patched versions to mitigate this risk. Additionally, utilizing tools like Vulert can help monitor and manage vulnerabilities effectively.
See every vulnerability recorded for typo3/cms →
FAQ
TYPO3 versions 6.0.x before 6.0.9 and 6.1.x before 6.1.4 are affected by this vulnerability.
If your TYPO3 installation is vulnerable, authenticated users could execute arbitrary PHP code, leading to potential data breaches and unauthorized access.
You can use Vulert, which monitors and alerts for open-source vulnerabilities in your software. Visit Vulert Scanner to check if your application is affected without needing to sign up.
Yes, you can temporarily restrict access to file management features for authenticated users until the patch is applied.
Vulert is a tool that monitors open-source vulnerabilities in your software using the composer.lock file. It provides real-time alerts and insights into potential security issues.
References
Related vulnerabilities
Recent vulnerabilities recorded for typo3/cms.
