dbcve.org
TYPO3CMS

CVE-2013-4250

MEDIUM · 6.5 CVSS v2.0 Published 2014-05-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The (1) file upload component and (2) File Abstraction Layer (FAL) in TYPO3 6.0.x before 6.0.8 and 6.1.x before 6.1.3 do not properly check file extensions, which allow remote authenticated editors to execute arbitrary PHP code by uploading a .php file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

TYPO3 6.0.x before 6.0.8 and 6.1.x before 6.1.3 have improper file extension validation in both the file upload component and the File Abstraction Layer (FAL). Authenticated editors can upload files with .php extensions, which the system accepts without proper validation, leading to arbitrary PHP code execution on the server.

MitigationUpgrade TYPO3 to version 6.0.8 or 6.1.3 or later. Alternatively, implement strict file extension deny-lists in the FAL configuration to block PHP file uploads from editor accounts.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TYPO3CMS
Affected:= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5= 6.0.6= 6.0.7= 6.0.9= 6.1= 6.1.1= 6.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed TYPO3 version
    Log into the TYPO3 backend as administrator and navigate to the 'About' module (or check the typo3conf/localconf.php file for the version constant). Alternatively, check the VERSION and SUB_VERSION constants in typo3/sysext/core/Classes/Utility/GeneralUtility.php or the installer metadata.
    Affected if The installed version is 6.0.0 through 6.0.7, or 6.1.0 through 6.1.2 (6.0.8 and 6.1.3 and later are fixed).
  2. Verify editor user accounts exist
    In the TYPO3 backend, navigate to the 'User Management' module (Admin Tools > User Management) and check for users with 'Editor' or similar limited privileges who have access to the file upload functionality.
    Affected if There are authenticated editor-level users in the system who have permissions to upload files.
  3. Check FAL storage configuration for extension validation
    Navigate to the File Abstraction Layer (FAL) storage configuration in the TYPO3 backend (filelist module > list view > click on a storage folder). Inspect the storage record in the database table 'sys_file_storage' or check the 'fileDenyPattern' and allowed extensions in the TYPO3 install tool configuration (typo3conf/localconf.php or typo3conf/LocalConfiguration.php).
    Affected if The file extension validation is either missing, permissive, or the 'fileDenyPattern' does not block .php file uploads, or no explicit allowlist is configured.
  4. Test file upload capability with a benign file
    Using an editor-level user account, attempt to upload a file through the file upload component in the TYPO3 backend (typically via the 'Filelist' module or any content element with file attachment capability). Observe whether the upload succeeds.
    Affected if The system accepts file uploads from editor accounts without rejecting .php or other executable extensions.

A system is affected if it runs TYPO3 version 6.0.0-6.0.7 or 6.1.0-6.1.2, has editor users with file upload permissions, and the FAL upload component does not properly validate or block .php file extensions.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade TYPO3 to version 6.0.8 or 6.1.3 or later. Alternatively, implement strict file extension deny-lists in the FAL configuration to block PHP file uploads from editor accounts.

Fix this in TYPO3 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-4250 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2013-4250 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data