MediumGHSA-594h-cx6w-p4jfCVE-2014-3941

Typo3 Host Header Spoofing Vulnerability

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

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 allows remote attackers to have unspecified impact via a crafted HTTP Host header, related to "Host Spoofing."

Is GHSA-594h-cx6w-p4jf 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.