TYPO3CMS
CVE-2011-4626
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 "JSwindow" property of the typolink 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 confidenceCross-site Scripting (XSS) vulnerability in TYPO3's typolink function where the JSwindow property does not properly sanitize user input, allowing remote attackers to inject arbitrary web script or HTML via specially crafted links.
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.
-
Determine installed TYPO3 versionCheck the TYPO3 version file. In older TYPO3 installations, look for a version indicator in typo3/version, typo3/sysext/core/VersionNumber.php, or the install tool System Information. The version is typically displayed in the TYPO3 backend footer or can be retrieved via the install tool.Affected if The installed version falls within 4.3.0 to 4.3.11, 4.4.0 to 4.4.8, or 4.5.0 to 4.5.3
-
Identify typolink usage with JSwindowSearch the TYPO3 installation codebase for typolink function calls that include the JSwindow parameter. Search PHP files for patterns like 'typolink(' or 'JSwindow' using grep or similar tools. Check extension PHP files and TypoScript templates.Affected if The codebase contains typolink calls using the JSwindow parameter, such as $this->cObj->typolink('', array('parameter' => '...', 'JSwindow' => '...')) or similar patterns
-
Inspect typolink JSwindow configurationReview TypoScript configuration files (setup.txt, typoscript templates) for typolink configurations that set JSwindow properties. Examine any custom extensions that may invoke the typolink function with user-influenced JSwindow parameters.Affected if TypoScript or extension code exposes JSwindow parameters that could accept user-supplied input without sanitization
-
Verify user input pathways to typolinkExamine how links are generated in the frontend. Trace the data flow from user inputs (URL parameters, form submissions, content fields) to typolink function calls. Determine if any user-controllable data reaches the JSwindow parameter.Affected if User-provided data can reach the JSwindow parameter of the typolink function without server-side validation
Your environment is affected if TYPO3 version is between 4.3.0 and 4.3.11, 4.4.0 and 4.4.8, or 4.5.0 and 4.5.3, AND the typolink function with JSwindow parameter is in use with potentially unsanitized 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 TYPO3 to version 4.3.12, 4.4.9, or 4.5.4 or later. If immediate patching is not possible, apply input validation/sanitization to the JSwindow parameter in the typolink function.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2011-4626 — 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-4626 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