Information Disclosure in typo3/cms-install tool
Published 14 Nov 2023 · Updated 10 Sept 2026
Is your project on an affected typo3/cms-install?
Look after several Laravel or PHP apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Affected package
- Affected
- >=12.2.0 <12.4.8
- Fixed in
- 12.4.8
composer require typo3/cms-install:^12.4.8Details
> ### CVSS: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C (3.5)
Problem
The login screen of the standalone install tool discloses the full path of the transient data directory (e.g. _/var/www/html/var/transient/_). This applies to composer-based scenarios only - “classic” non-composer installations are not affected.
Solution
Update to TYPO3 version 12.4.8 that fixes the problem described above.
Credits
Thanks to Markus Klein who reported and fixed the issue.
References
Is GHSA-p2jh-95jg-2w55 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-install, and gives you the command that fixes it.
More advisories for typo3/cms-install
- LowCVE-2024-55891TYPO3 Information Disclosure via Exception Handling/Logger · 14 Jan 2025
- LowCVE-2010-5100TYPO3 Cross-Site Scripting vulnerability in the Install Tool · 17 May 2022
- MediumCVE-2009-3636Typo3 API Install Tool vulnerable to Cross-site Scripting · 2 May 2022
- MediumCVE-2010-3666TYPO3 is vulnerable to Insecure randomness in uniqid function · 21 Apr 2022
- MediumCVE-2010-3671TYPO3 is vulnerable to Session Fixation · 21 Apr 2022
References
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.