Security readout for executives and security teams
Plain-English summary
This issue affects old TYPO3 releases and could let a remote attacker inject script or HTML through TYPO3’s typolink JSwindow property. In business terms, exposed legacy TYPO3 sites may allow browser-side compromise of visitors or administrators. The source bundle does not show active exploitation or a CVSS score.
Executive priority
Treat this as a legacy-web-platform risk. It is not shown as actively exploited in the provided evidence, but any internet-facing affected TYPO3 instance should be upgraded or retired promptly because XSS can harm users and administrators.
Technical view
CVE-2011-4626 is a cross-site scripting flaw in TYPO3 before 4.3.12, 4.4.x before 4.4.9, and 4.5.x before 4.5.4. The vulnerable input is the JSwindow property of the typolink function. Available sources do not provide CVSS, CWE, or exploit details.
Likely exposure
Exposure is most likely on internet-facing TYPO3 installations still running the listed legacy versions, especially where affected typolink functionality is used. Modern or upgraded TYPO3 deployments are not indicated as affected by the provided sources.
Exploitation context
The bundle marks KEV as false and provides no cited evidence of active exploitation. The impact is browser-side script or HTML injection, which may affect users interacting with vulnerable TYPO3-generated content.
Researcher notes
Evidence is limited: no CVSS, CWE, or exploit-status detail is supplied. The strongest source-grounded facts are the affected TYPO3 version ranges, the XSS class, and the JSwindow property in typolink as the vulnerable area.
Mitigation direction
- Upgrade TYPO3 to 4.3.12, 4.4.9, 4.5.4, or a later supported release.
- Check the TYPO3 advisory for version-specific remediation guidance.
- Prioritize retirement or isolation of unsupported legacy TYPO3 instances.
- Review exposed TYPO3 sites for untrusted typolink JSwindow usage.
Validation and detection
- Inventory all TYPO3 deployments and confirm exact core versions.
- Compare installed versions against 4.3.12, 4.4.9, and 4.5.4 fixed thresholds.
- Confirm no public production site runs an affected legacy branch.
- Review change records for completed TYPO3 security updates.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CVE-2011-4626 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://security-tracker.debian.org/tracker/CVE-2011-4626CVE reference · x_refsource_MISC
- https://typo3.org/security/advisory/typo3-core-sa-2011-001/#XSSCVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.