MediumGHSA-9c6w-55cp-5w25BIT-typo3-2022-36107CVE-2022-36107

TYPO3 CMS Stored Cross-Site Scripting via FileDumpController

Published 16 Sept 2022 · Updated 6 Dec 2023

Affected packages

typo3/cms-coreComposer
Affected
>=7.0.0 <7.6.58
Fixed in
7.6.58
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^7.6.58
typo3/cms-coreComposer
Affected
>=8.0.0 <8.7.48
Fixed in
8.7.48
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^8.7.48
typo3/cms-coreComposer
Affected
>=9.0.0 <9.5.37
Fixed in
9.5.37
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.37
typo3/cms-coreComposer
Affected
>=10.0.0 <10.4.32
Fixed in
10.4.32
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.32
typo3/cms-coreComposer
Affected
>=11.0.0 <11.5.16
Fixed in
11.5.16
Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.16
typo3/cmsComposer
Affected
>=10.0.0 <10.4.32
Fixed in
10.4.32
Update to the fixed version for your release line, for example:composer require typo3/cms:^10.4.32
typo3/cmsComposer
Affected
>=11.0.0 <11.5.16
Fixed in
11.5.16
Update to the fixed version for your release line, for example:composer require typo3/cms:^11.5.16

Details

> ### Meta > * CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C (5.0)

Problem

It has been discovered that the FileDumpController (backend and frontend context) is vulnerable to cross-site scripting when malicious files are displayed using this component. A valid backend user account is needed to exploit this vulnerability.

Solution

Update to TYPO3 version 7.6.58 ELTS, 8.7.48 ELTS, 9.5.37 ELTS, 10.4.32 or 11.5.16 that fix the problem described above.

Credits

Thanks to Vautia who reported this issue and to TYPO3 core & security team member Oliver Hader who fixed the issue.

References

Is GHSA-9c6w-55cp-5w25 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.