TYPO3CMS
CVE-2011-4904
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.4.9 and 4.5.x before 4.5.4 does not apply proper access control on ExtDirect calls which allows remote attackers to retrieve ExtDirect endpoint services.
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 confidenceTYPO3 before versions 4.4.9 and 4.5.4 fails to enforce proper access control on ExtDirect API calls, allowing unauthenticated remote attackers to enumerate and retrieve ExtDirect endpoint services. ExtDirect is a server-side API framework in TYPO3 that exposes server methods to JavaScript clients, and the lack of authorization checks permits unauthorized access to these services.
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.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.
-
Identify installed TYPO3 versionCheck the version.php file in the TYPO3 root directory (e.g., /typo3/version.php) or access the TYPO3 admin panel and look for the version information in the About moduleAffected if The installed version is >= 4.4.0 and < 4.4.9, OR >= 4.5.0 and < 4.5.4
-
Verify ExtDirect endpoint existenceLook for the ExtDirect API endpoint file at /typo3/mod/extdevenv/ or /typo3/tce/ in the web root. Alternatively, check the TYPO3 installation for files containing 'ExtDirect' or 'extdirect' in the typo3conf/ directoryAffected if ExtDirect endpoint files exist in the installation and are web-accessible
-
Test unauthenticated ExtDirect accessSend an HTTP request to the ExtDirect endpoint (typically at /typo3/mod/extdevenv/ or /typo3/tce/) without providing authentication credentials. Use a tool like curl: curl -s http://your-server/typo3/mod/extdevenv/Affected if The endpoint returns a valid response (HTTP 200) without requiring login or session authentication
-
Check for ExtDirect service enumerationSend a request to the ExtDirect endpoint with a basic introspection call (such as {"action":"ExtDirect","method":"describe","type":"rpc","tid":1}) and observe if the response reveals available services and methodsAffected if The response contains a list of exposed TYPO3 services, methods, or class definitions without authentication
You are affected if your TYPO3 installation is version 4.4.0 through 4.4.8 or 4.5.0 through 4.5.3 AND the ExtDirect endpoint is accessible without authentication.
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.4.94.5.4
Upgrade TYPO3 to version 4.4.9, 4.5.4, or later to obtain the patched version that properly implements access control on ExtDirect calls. If upgrading is not immediately feasible, review and restrict ExtDirect endpoint exposure through web server configuration or firewall rules.
Fix this in TYPO3
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4904 — 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-4904 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