MediumGHSA-mxjf-hc9v-xgv2

ExtJS JavaScript framework used in TYPO3 vulnerable to Cross-site Scripting

Published 30 May 2024 · Updated 6 Dec 2024

Affected packages

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
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
>=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
>=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

Details

Failing to properly validate the HTTP host-header TYPO3 CMS is susceptible to host spoofing. TYPO3 uses the HTTP host-header to generate absolute URLs in several places like 404 handling, http(s) enforcement, password reset links and many more. Since the host header itself is provided by the client it can be forged to any value, even in a name based virtual hosts environment. A blog post describes this problem in great detail.

Is GHSA-mxjf-hc9v-xgv2 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.