MediumGHSA-cg75-qfg2-w9hjCVE-2026-47348

TYPO3 CMS has Cross-Site Scripting in Indexed Search

Published 12 Jun 2026 · Updated 10 Sept 2026

Affected packages

typo3/cms-coreComposer

Affected: >=13.0.0 <13.4.31
Fixed in: 13.4.31

Update to the fixed version for your release line, for example:composer require typo3/cms-core:^13.4.31

typo3/cms-coreComposer

Affected: >=14.0.0 <14.3.3
Fixed in: 14.3.3

Update to the fixed version for your release line, for example:composer require typo3/cms-core:^14.3.3

typo3/cms-indexed-searchComposer

Affected: >=13.0.0 <13.4.31
Fixed in: 13.4.31

Update to the fixed version for your release line, for example:composer require typo3/cms-indexed-search:^13.4.31

typo3/cms-indexed-searchComposer

Affected: >=14.0.0 <14.3.3
Fixed in: 14.3.3

Update to the fixed version for your release line, for example:composer require typo3/cms-indexed-search:^14.3.3

Details

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.

Solution

Update to TYPO3 versions 13.4.31 LTS, 14.3.3 LTS that fix the problem described.

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

TYPO3-CORE-SA-2026-010

Is GHSA-cg75-qfg2-w9hj in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-core, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.