TYPO3CMS
CVE-2013-4321
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 · uneditedThe File Abstraction Layer (FAL) in TYPO3 6.0.x before 6.0.8 and 6.1.x before 6.1.4 allows remote authenticated editors to execute arbitrary PHP code via unspecified characters in the file extension when renaming a file. NOTE: this vulnerability exists because of an incomplete fix for CVE-2013-4250.
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 · moderate confidenceThe File Abstraction Layer (FAL) in TYPO3 6.0.x before 6.0.8 and 6.1.x before 6.1.4 allows authenticated editors to execute arbitrary PHP code by embedding malicious PHP code in file extensions during file rename operations. This vulnerability exists as an incomplete fix for CVE-2013-4250, suggesting the previous patch failed to properly sanitize all dangerous extension characters.
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
= 6.1= 6.1.1= 6.1.2= 6.1.3= 6.0= 6.0.1= 6.0.2= 6.0.3= 6.0.4= 6.0.5= 6.0.6= 6.0.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed TYPO3 versionLocate the TYPO3 version file or admin panel version display. This is typically found in the TYPO3 core installation directory or accessible via the admin backend under 'Help' > 'About'.Affected if The installed version is 6.0.x where x is less than 8, or 6.1.x where x is less than 4 (6.0.0 through 6.0.7, or 6.1.0 through 6.1.3).
-
Confirm File Abstraction Layer (FAL) is in useVerify that the TYPO3 installation uses FAL for file handling. In TYPO3 6.0.x and 6.1.x, FAL is the default file handling system and is enabled by default.Affected if FAL is the active file handling mechanism (which is the default state in affected versions).
-
Verify editor-level user accounts existCheck for user accounts with editor-level permissions in the TYPO3 backend user administration module.Affected if Editor or higher-privileged user accounts exist who can access file rename functionality.
-
Check if file rename permissions are granted to editorsInspect the backend user group permissions, specifically looking at file operation permissions under the 'File > Rename' or equivalent file action rights.Affected if Editor users have permission to rename files in the file backend.
A system is affected if it runs any TYPO3 version between 6.0.0 and 6.0.7 or between 6.1.0 and 6.1.3, uses the FAL system, and has editor-level users with file rename permissions.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade TYPO3 to version 6.0.8, 6.1.4, or later to obtain the complete fix for this vulnerability. Additionally, restrict editor permissions to file operations until the upgrade is applied.
Fix this in TYPO3
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4321 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-4321 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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