TYPO3CMS
CVE-2011-4631
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 system extension recycler.
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 confidenceCross-site scripting (XSS) vulnerability in the TYPO3 system extension 'recycler' allows remote attackers to inject arbitrary JavaScript or HTML via unsanitized input. This affects TYPO3 versions 4.3.x before 4.3.12, 4.4.x before 4.4.9, and 4.5.x before 4.5.4. The vulnerability is exploitable without authentication in the recycler extension.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Determine installed TYPO3 versionCheck the TYPO3 version by viewing the backend footer, or by checking the version file in the TYPO3 source (such as 'typo3/sysext/core/Classes/Utility/GeneralUtility.php' containing the version constant), or by running the command-line typo3/cli script if availableAffected if The displayed or detected version falls within 4.3.0 to 4.3.11, or 4.4.0 to 4.4.8, or 4.5.0 to 4.5.3 inclusive
-
Verify recycler extension presenceCheck if the recycler extension is installed by looking for the directory 'typo3conf/ext/recycler' or by examining the Extension Manager in the TYPO3 backend under 'Installed Extensions'Affected if The recycler extension directory exists in typo3conf/ext/ or the extension shows as installed in the Extension Manager
-
Confirm recycler extension is enabledInspect the extension configuration file (such as PackageStates.php in newer versions or localconf.php in older versions) to verify the recycler extension is marked as active, or check via the Extension Manager that the extension is not unloadedAffected if The recycler extension is loaded and active in the TYPO3 installation
You are affected if your TYPO3 version is between 4.3.0-4.3.11, 4.4.0-4.4.8, or 4.5.0-4.5.3 AND the recycler extension is installed and enabled.
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 patch the vulnerable recycler extension. If upgrading is not feasible, disable or remove the recycler extension until patching can be performed.
Fix this in TYPO3
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4631 — 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-4631 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