TYPO3CMS
CVE-2011-4903
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 · uneditedCross-site Scripting (XSS) in TYPO3 before 4.3.12, 4.4.x before 4.4.9, and 4.5.x before 4.5.4 allows remote attackers to inject arbitrary web script or HTML via the RemoveXSS function.
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 RemoveXSS function in TYPO3, intended to sanitize user input and prevent cross-site scripting attacks, contains a vulnerability that allows remote attackers to inject arbitrary web script or HTML. This affects TYPO3 versions prior to 4.3.12, 4.4.x before 4.4.9, and 4.5.x before 4.5.4.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 versionLocate the TYPO3 version file (usually typo3/sysext/core/Classes/Utility/GeneralUtility.php or check the 'TYPO3_version' constant in typo3/init.php). Alternatively, access the TYPO3 admin panel and check 'Help > About' or look at the VERSION file in the TYPO3 root directory.Affected if The version is 4.3.x before 4.3.12, or 4.4.x before 4.4.9, or 4.5.x before 4.5.4.
-
Locate RemoveXSS function implementationSearch the TYPO3 source code for the RemoveXSS function definition. This is typically found in typo3/sysext/core/Classes/Utility/GeneralUtility.php or similar core utility files. Look for function removeXSS or function RemoveXSS.Affected if The function exists in the codebase (it is present in all affected versions listed).
-
Verify RemoveXSS is in use by the applicationSearch the codebase for calls to removeXSS, such as GeneralUtility::removeXSS() or similar invocations. Check template files, extensions, and custom PHP code that processes user input.Affected if The RemoveXSS function is being called to sanitize user-supplied data (the vulnerability only matters when this function is actually used).
You are affected if your TYPO3 installation version falls within the ranges 4.3.0-4.3.11, 4.4.0-4.4.8, or 4.5.0-4.5.3 AND the RemoveXSS function is actively used to sanitize user input.
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 versions which contain the fix for the vulnerable RemoveXSS function.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4903 — 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-4903 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