HighGHSA-2rxh-h6h9-qrqcBIT-typo3-2020-11066CVE-2020-11066

Class destructors causing side-effects when being unserialized in TYPO3 CMS

Published 13 May 2020 · Updated 10 Sept 2026

Affected packages

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

Details

Calling unserialize() on malicious user-submitted content can result in the following scenarios:

  • trigger deletion of arbitrary directory in file system (if writable for web server)
  • trigger message submission via email using identity of web site (mail relay)

Another insecure deserialization vulnerability is required to actually exploit mentioned aspects.

Update to TYPO3 versions 9.5.17 or 10.4.2 that fix the problem described.

References

  • https://typo3.org/security/advisory/typo3-core-sa-2020-004

Is GHSA-2rxh-h6h9-qrqc 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.