TYPO3CMS
CVE-2013-4320
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.9 and 6.1.x before 6.1.4 does not properly check permissions, which allows remote authenticated users to create or read arbitrary files via a crafted URL.
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 confidenceThe File Abstraction Layer (FAL) in TYPO3 6.0.x before 6.0.9 and 6.1.x before 6.1.4 lacks proper permission validation, allowing authenticated remote users to manipulate file paths through crafted URLs to create or read arbitrary files on the server - consistent with a path traversal vulnerability.
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
- None
AV:N/AC:L/Au:S/C:P/I:P/A:N
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 installed TYPO3 versionCheck the TYPO3 version by viewing the 'typo3/sysext/core/Classes/Utility/GeneralUtility.php' file or accessing the TYPO3 admin panel (About module). Alternatively, check the 'typo3/version' file if it exists.Affected if The installed version is 6.0.x before 6.0.9 or 6.1.x before 6.1.4 (specifically 6.0, 6.0.1, 6.0.2, 6.0.3, 6.0.4, 6.0.5, 6.0.6, 6.0.7, 6.1, 6.1.1, 6.1.2, or 6.1.3)
-
Confirm FAL module is in useVerify that the File Abstraction Layer (FAL) extension is loaded and actively used for file management. Check the 'typo3conf/ext/' directory for FAL-related extensions or review the TYPO3 extension list in the backend.Affected if FAL is enabled and the TYPO3 version falls within the vulnerable range listed above
-
Review file upload and processing functionalityIdentify any custom or core functionalities that accept file paths or allow file operations through URL parameters. Inspect any controllers handling file references, particularly in extensions using FAL file processing.Affected if The application accepts file path input through URL parameters without strict validation, combined with an affected TYPO3 version
-
Check file permission configurationReview the file mount configurations and typo3conf/localconf.php or typo3conf/LocalConfiguration.php for file permission settings. Look for overly permissive file mount points that may allow path traversal.Affected if File mounts are configured with broad permissions that allow access outside intended directories, on a vulnerable TYPO3 version
You are affected if TYPO3 version is 6.0.x before 6.0.9 or 6.1.x before 6.1.4 AND the FAL component is in use with file operations accessible to authenticated users.
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.9, 6.1.4, or later to obtain the patched FAL component; alternatively, apply the specific security patch for this issue and review file permission configurations.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-4320 — 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-4320 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