MediumGHSA-m2jh-fxw4-gphmBIT-typo3-2021-41114CVE-2021-41114

HTTP Host Header Injection

Published 5 Oct 2021 · Updated 8 Jul 2026

Affected packages

typo3/cms-coreComposer
Affected
>=11.0.0 <11.5.0
Fixed in
11.5.0
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.0
typo3/cmsComposer
Affected
>=11.0.0 <11.5.0
Fixed in
11.5.0
Update to the fixed version for your release line, for example:composer require typo3/cms:^11.5.0

Details

Meta

  • CVSS: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N/E:F/RL:O/RC:C (3.5)

Problem

It has been discovered that TYPO3 CMS is susceptible to host spoofing due to improper validation of the HTTP _Host_ header. TYPO3 uses the HTTP _Host_ header, for example, to generate absolute URLs during the frontend rendering process. 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.

This vulnerability is the same as described in TYPO3-CORE-SA-2014-001 (CVE-2014-3941). A regression, introduced during TYPO3 v11 development, led to this situation. The already existing setting _$GLOBALS['TYPO3_CONF_VARS']['SYS']['trustedHostsPattern']_ (used as an effective mitigation strategy in previous TYPO3 versions) was not evaluated anymore, and reintroduced the vulnerability.

Solution

Update your instance to TYPO3 version 11.5.0 which addresses the problem described.

Credits

Thanks to TYPO3 framework merger Benjamin Franzke who reported and fixed the issue.

References

Is GHSA-m2jh-fxw4-gphm 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 signupOr connect GitHub to scan every repo

References

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