CVE-2013-4250: TYPO3 CMS File Upload Vulnerability Leading to Remote Code Execution
Summary
CVE-2013-4250: TYPO3 doesn't properly check file extensions. Affects typo3/cms across 2 version ranges.
>= 6.0.0, < 6.0.8
>= 6.1.0, < 6.1.3
Fixed in 6.0.8 or 6.1.3, 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
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
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, allowing for extensive customization and scalability. However, certain versions of TYPO3 have been found to be vulnerable due to improper file extension checks in its file upload component and File Abstraction Layer (FAL), which can lead to severe security risks.
Vulnerability Detail
The vulnerability arises from TYPO3's failure to adequately validate file extensions during the upload process. Specifically, in versions 6.0.x prior to 6.0.8 and 6.1.x prior to 6.1.3, authenticated users could upload malicious .php files. This oversight allows attackers to execute arbitrary PHP code on the server, potentially leading to unauthorized access, data breaches, or complete server compromise. The vulnerability is classified under CWE-20 (Improper Input Validation) and CWE-434 (Unrestricted Upload of File with Dangerous Type).
How To Fix
Fixed versions by release line
The minimum fixed version depends on the release line you run.
-
>= 6.0.0, < 6.0.86.0.8composer require typo3/cms:6.0.8 -
>= 6.1.0, < 6.1.36.1.3composer require typo3/cms:6.1.3
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, administrators can restrict file uploads to only allow specific file types and implement additional server-side checks to validate file contents before processing uploads. This can be achieved by modifying the server configuration or using custom scripts to filter uploaded files.
Conclusion
The TYPO3 vulnerability CVE-2013-4250 highlights a critical security flaw in the file upload mechanism of certain versions of the CMS. It is essential for users to update to the latest patched versions to safeguard against potential exploitation. Implementing additional security measures can further enhance protection against such vulnerabilities.
See every vulnerability recorded for typo3/cms →
FAQ
TYPO3 versions 6.0.x before 6.0.8 and 6.1.x before 6.1.3 are affected by this vulnerability.
If exploited, this vulnerability can allow attackers to execute arbitrary PHP code, leading to unauthorized access and potential server compromise.
You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.
Yes, you can implement server-side checks to restrict file uploads to safe types and validate file contents before processing.
Vulert monitors and alerts for open-source vulnerabilities in your software using just the composer.lock file, providing real-time insights into potential risks.
References
Related vulnerabilities
Recent vulnerabilities recorded for typo3/cms.
Habilume
Habit tracker with a companion that grows with you
Complete habits, earn Lume Points, and watch your Lume grow as you stay consistent.
