MediumGHSA-8mq9-fqv8-59wfBIT-typo3-2021-32667CVE-2021-32667

Cross-Site Scripting in Page Preview

Published 22 Jul 2021 · Updated 8 Jul 2026

Affected packages

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

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

Problem

Failing to properly encode _Page TSconfig_ settings, corresponding page preview module (_Web>View_) is vulnerable to persistent cross-site scripting. A valid backend user account is needed to exploit this vulnerability.

Solution

Update to TYPO3 versions 9.5.28, 10.4.18, 11.3.1 that fix the problem described.

Credits

Thanks to TYPO3 core merger Oliver Bartsch who reported and fixed the issue.

References

Is GHSA-8mq9-fqv8-59wf 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.

References

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