TYPO3CMS
CVE-2011-4902
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 · uneditedTYPO3 before 4.3.12, 4.4.x before 4.4.9, and 4.5.x before 4.5.4 allows remote attackers to delete arbitrary files on the webserver.
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 confidenceThis is a file deletion vulnerability in TYPO3 CMS versions prior to 4.3.12, 4.4.9, and 4.5.4. The vulnerability allows remote authenticated attackers to delete arbitrary files on the webserver through improper input validation or path traversal in the application, potentially leading to denial of service or data loss.
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
>= 4.3.0, < 4.3.12>= 4.4.0, < 4.4.9>= 4.5.0, < 4.5.4CVSS 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
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 TYPO3 installation and versionCheck the TYPO3 version file, typically located at typo3/sysext/core/typo3/sysext/core/Compatibility.php or look for a version marker in typo3conf/localconf.php. The version is also displayed on the TYPO3 login page footer or in the Admin Tools > About section.Affected if The installed version falls within one of these ranges: 4.3.0 to 4.3.11, 4.4.0 to 4.4.8, or 4.5.0 to 4.5.3
-
Verify the file deletion functionality existsCheck if the TYPO3 file management modules (such as filelist or fileadmin) are accessible. These modules handle file operations and may contain the vulnerable code. Inspect the installed system extensions in typo3/sysext/ for filelist or similar file handling extensions.Affected if File management extensions are installed and accessible to authenticated users
-
Confirm authentication is enabledVerify that TYPO3 user authentication is enabled. Check typo3conf/localconf.php for enabled authentication modes and ensure the install tool password has been changed from default. The vulnerability requires an authenticated attacker.Affected if Authentication is enabled and user accounts exist with access to file management features
You are affected if TYPO3 is installed with a version between 4.3.0 and 4.3.11, 4.4.0 and 4.4.8, or 4.5.0 and 4.5.3, and file management modules are 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 data4.3.124.4.94.5.4
Upgrade TYPO3 to version 4.3.12, 4.4.9, 4.5.4 or later to receive the patch. If immediate patching is not possible, restrict administrative access to trusted users only and implement file system permissions that limit the web server process write access to essential directories only.
Fix this in TYPO3
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4902 — 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-2011-4902 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