TYPO3CMS
CVE-2011-4901
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 extract arbitrary information from the TYPO3 database.
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 confidenceThis is an information disclosure vulnerability in older TYPO3 CMS versions (before 4.3.12, 4.4.x before 4.4.9, and 4.5.x before 4.5.4) that allows remote attackers to extract arbitrary information from the TYPO3 database, likely via SQL injection or similar data exfiltration mechanism.
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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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.
-
Locate TYPO3 installation directoryIdentify the web root directory where TYPO3 is installed. Common paths include /typo3/ or / typo3_src/ within the web directory.Affected if Cannot proceed without locating the TYPO3 installation
-
Identify installed TYPO3 versionCheck the TYPO3 version file. In legacy TYPO3 4.x, open typo3/sysext/core/Classes/Utility/GeneralUtility.php and search for a line containing 'VERSION' or check the install tool at /typo3/install/ which displays the version on the first screen.Affected if The version cannot be determined from the installation
-
Compare version against affected rangesIf the installed version is 4.3.x, check if it is below 4.3.12. If 4.4.x, check if below 4.4.9. If 4.5.x, check if below 4.5.4. Any version in the ranges 4.3.0-4.3.11, 4.4.0-4.4.8, or 4.5.0-4.5.3 is affected.Affected if Installed version falls within >= 4.3.0 < 4.3.12, or >= 4.4.0 < 4.4.9, or >= 4.5.0 < 4.5.4
-
Verify TYPO3 is accessible over networkConfirm the TYPO3 instance is reachable via HTTP/HTTPS. The vulnerability is exploitable remotely, so an inaccessible or internal-only instance has reduced exposure.Affected if TYPO3 is publicly accessible on the network
A TYPO3 installation is affected if it is running version 4.3.0 through 4.3.11, 4.4.0 through 4.4.8, or 4.5.0 through 4.5.3 and is network-accessible.
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 to TYPO3 4.3.12, 4.4.9, 4.5.4 or later. Note that these are extremely legacy versions (2011 era) and a full migration to a supported TYPO3 version may be required rather than a minor version bump.
Fix this in TYPO3
Scoped from the published advisory
- Consultation4.0 h
- Implementation16.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,960.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4901 — 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-4901 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