Summary
Cross-site scripting (XSS) vulnerability in the t3lib_div::quoteJSvalue API function in TYPO3 4.0.13 and earlier, 4.1.x before 4.1.13, 4.2.x before 4.2.10, and 4.3.x before 4.3beta2 allows remote attackers to inject arbitrary web script or HTML via unspecified vectors related to the sanitizing algorithm.
Impact
A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
typo3/cms-core to 4.1.13 or later; typo3/cms-core to 4.2.10 or later; typo3/cms-core to 4.3beta2 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2009-3633? CVE-2009-3633 is a medium-severity cross-site request forgery (CSRF) vulnerability in typo3/cms-core (composer), affecting versions <= 4.0.13. It is fixed in 4.1.13, 4.2.10, 4.3beta2. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
- Which versions of typo3/cms-core are affected by CVE-2009-3633? typo3/cms-core (composer) versions <= 4.0.13 is affected.
- Is there a fix for CVE-2009-3633? Yes. CVE-2009-3633 is fixed in 4.1.13, 4.2.10, 4.3beta2. Upgrade to this version or later.
- Is CVE-2009-3633 exploitable, and should I be worried? Whether CVE-2009-3633 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2009-3633 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2009-3633?
- Upgrade
typo3/cms-coreto 4.1.13 or later - Upgrade
typo3/cms-coreto 4.2.10 or later - Upgrade
typo3/cms-coreto 4.3beta2 or later
- Upgrade