CVE-2022-36107

Meta

• CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C (5.0)

Problem

It has been discovered that the FileDumpController (backend and frontend context) is vulnerable to cross-site scripting when malicious files are displayed using this component. A valid backend user account is needed to exploit this vulnerability.

Credits

Thanks to Vautia who reported this issue and to TYPO3 core & security team member Oliver Hader who fixed the issue.

References

• TYPO3-CORE-SA-2022-009
• Vulnerability Report on huntr.dev (embargoed +30 days)

Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.

CVE-2022-36107 has a CVSS score of 5.4 (Medium). The vector is network-reachable, low privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.6.58, 8.7.48, 9.5.37, 10.4.32, 11.5.16); upgrading removes the vulnerable code path.

Kodem intelligence

Update to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.

1. What is CVE-2022-36107? CVE-2022-36107 is a medium-severity cross-site scripting (XSS) vulnerability in typo3/cms-core (composer), affecting versions >= 7.0.0, < 7.6.58. It is fixed in 7.6.58, 8.7.48, 9.5.37, 10.4.32, 11.5.16. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2022-36107? CVE-2022-36107 has a CVSS score of 5.4 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-36107?
   • typo3/cms-core (composer) (versions >= 7.0.0, < 7.6.58)
   • typo3/cms (composer) (versions >= 10.0.0, < 10.4.32)
4. Is there a fix for CVE-2022-36107? Yes. CVE-2022-36107 is fixed in 7.6.58, 8.7.48, 9.5.37, 10.4.32, 11.5.16. Upgrade to this version or later.
5. Is CVE-2022-36107 exploitable, and should I be worried? Whether CVE-2022-36107 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
6. What actually determines whether CVE-2022-36107 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.
7. How do I fix CVE-2022-36107?
   • Upgrade typo3/cms-core to 7.6.58 or later
   • Upgrade typo3/cms-core to 8.7.48 or later
   • Upgrade typo3/cms-core to 9.5.37 or later
   • Upgrade typo3/cms-core to 10.4.32 or later
   • Upgrade typo3/cms-core to 11.5.16 or later
   • Upgrade typo3/cms to 10.4.32 or later
   • Upgrade typo3/cms to 11.5.16 or later