MediumGHSA-c7rj-92xr-wprg

Insecure Unserialize in TYPO3 Backend

Published 5 Jun 2024 · Updated 2 Dec 2024

Affected packages

typo3/cmsComposer

Affected: >=6.2.0 <6.2.29
Fixed in: 6.2.29

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

typo3/cmsComposer

Affected: >=7.6.0 <7.6.13
Fixed in: 7.6.13

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

typo3/cmsComposer

Affected: >=8.0.0 <8.4.1
Fixed in: 8.4.1

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

Details

Failing to properly validate incoming data, the suggest wizard is susceptible to insecure unserialize. To exploit this vulnerability a valid backend user account is needed.

Is GHSA-c7rj-92xr-wprg 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, and gives you the command that fixes it.

Scan a project free, no signup Or connect GitHub to scan every repo

References

Linkgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/2016-11-22-1.yaml

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