Summary
TYPO3 CMS has Cross-Site Scripting in Indexed Search
Problem
Editors with access to create or modify page content were able to include HTML markup in page titles that were stored in the search index without sanitization. When displayed in frontend search results via the Indexed Search plugin, these titles were rendered without proper output encoding, resulting in a Cross-Site Scripting vulnerability.
Credits
TYPO3 CMS thanks Jan Kahmen and Sanjay Singh Jhala for reporting this issue, and to TYPO3 core & security team member Oliver Hader for fixing it.
Resources
Impact
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.
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.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Update to TYPO3 versions 13.4.31 LTS, 14.3.3 LTS that fix the problem described.
Frequently Asked Questions
- What is CVE-2026-47348? CVE-2026-47348 is a medium-severity cross-site scripting (XSS) vulnerability in typo3/cms-core (composer), affecting versions >= 13.0.0, < 13.4.31. It is fixed in 13.4.31, 14.3.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- Which packages are affected by CVE-2026-47348?
typo3/cms-core(composer) (versions >= 13.0.0, < 13.4.31)typo3/cms-indexed-search(composer) (versions >= 13.0.0, < 13.4.31)
- Is there a fix for CVE-2026-47348? Yes. CVE-2026-47348 is fixed in 13.4.31, 14.3.3. Upgrade to this version or later.
- Is CVE-2026-47348 exploitable, and should I be worried? Whether CVE-2026-47348 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-2026-47348 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-2026-47348?
- Upgrade
typo3/cms-coreto 13.4.31 or later - Upgrade
typo3/cms-coreto 14.3.3 or later - Upgrade
typo3/cms-indexed-searchto 13.4.31 or later - Upgrade
typo3/cms-indexed-searchto 14.3.3 or later
- Upgrade