LowGHSA-qqh2-h6gw-6x8xCVE-2014-3943

Typo3 XSS Vulnerabilities

Published 14 May 2022 · Updated 14 Apr 2025

Affected packages

typo3/cmsComposer
Affected
>=4.5.0 <4.5.34
Fixed in
4.5.34
Update to the fixed version for your release line, for example:composer require typo3/cms:^4.5.34
typo3/cmsComposer
Affected
>=4.7.0 <4.7.19
Fixed in
4.7.19
Update to the fixed version for your release line, for example:composer require typo3/cms:^4.7.19
typo3/cmsComposer
Affected
>=6.0.0 <6.0.14
Fixed in
6.0.14
Update to the fixed version for your release line, for example:composer require typo3/cms:^6.0.14
typo3/cmsComposer
Affected
>=6.1.0 <6.1.9
Fixed in
6.1.9
Update to the fixed version for your release line, for example:composer require typo3/cms:^6.1.9
typo3/cmsComposer
Affected
>=6.2.0 <6.2.3
Fixed in
6.2.3
Update to the fixed version for your release line, for example:composer require typo3/cms:^6.2.3

Details

Multiple cross-site scripting (XSS) vulnerabilities in unspecified backend components in TYPO3 4.5.0 before 4.5.34, 4.7.0 before 4.7.19, 6.0.0 before 6.0.14, 6.1.0 before 6.1.9, and 6.2.0 before 6.2.3 allow remote authenticated editors to inject arbitrary web script or HTML via unknown parameters.

Is GHSA-qqh2-h6gw-6x8x 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, and gives you the command that fixes it.

References

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