MediumGHSA-h4mx-xv96-2jgmBIT-typo3-2022-31049CVE-2022-31049

Cross-Site Scripting in TYPO3's Frontend Login Mailer

Published 17 Jun 2022 · Updated 6 Dec 2023

Affected packages

typo3/cms-coreComposer

Affected: >=9.0.0 <9.5.35
Fixed in: 9.5.35

Update to the fixed version for your release line, for example:composer require typo3/cms-core:^9.5.35

typo3/cms-coreComposer

Affected: >=10.0.0 <10.4.29
Fixed in: 10.4.29

Update to the fixed version for your release line, for example:composer require typo3/cms-core:^10.4.29

typo3/cms-coreComposer

Affected: >=11.0.0 <11.5.11
Fixed in: 11.5.11

Update to the fixed version for your release line, for example:composer require typo3/cms-core:^11.5.11

typo3/cmsComposer

Affected: >=10.0.0 <10.4.29
Fixed in: 10.4.29

Update to the fixed version for your release line, for example:composer require typo3/cms:^10.4.29

typo3/cmsComposer

Affected: >=11.0.0 <11.5.11
Fixed in: 11.5.11

Update to the fixed version for your release line, for example:composer require typo3/cms:^11.5.11

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 (4.9)

Problem

User submitted content was used without being properly encoded in HTML emails sent to users. The actually affected components were mail clients used to view those messages.

Solution

Update to TYPO3 versions 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above.

Credits

Thanks to Christian Seifert who reported this issue and to TYPO3 framework merger Andreas Fernandez who fixed the issue.

References

TYPO3-CORE-SA-2022-004

Is GHSA-h4mx-xv96-2jgm 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 signup Or connect GitHub to scan every repo

References

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