2016-11-22-1: Insecure Unserialize in TYPO3 Backend

unknown Affects typo3/cms. Feed 2026.10.29.3, updated 2026-10-29.

Insecure Unserialize in TYPO3 Backend

Package: typo3/cms Composer
Affected versions: >=6.2.0 and <6.2.29 or >=7.6.0 and <7.6.13 or >=8.0.0 and <8.1.0 or >=8.1.0 and <8.2.0 or >=8.2.0 and <8.3.0 or >=8.3.0 and <8.4.0 or >=8.4.0 and <8.4.1
Fixed in: 6.2.29, 7.6.13, 8.4.1
Severity: unknown
Exploitation: not on CISA KEV
Source: friendsofphp

References

https://typo3.org/teams/security/security-bulletins/typo3-core/typo3-core-sa-2016-023/

Am I affected?

Find out in one command. phpwarden checks your composer.lock against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden deps composer.lock

# or, without Composer
pipx install phpwarden   &&   phpwarden deps composer.lock

Or keep it checked automatically: GitHub Action · pre-commit hook · GitLab CI · Laravel artisan command

Install docs How findings are ranked

Related advisories

CVE-2016-5385 high HTTP Proxy header vulnerability same package: typo3/cms
CVE-2009-0815 medium TYPO3 leaks a hash secret in an error message same package: typo3/cms
CVE-2010-3714 high TYPO3 Remote File Disclosure vulnerability in the jumpUrl mechanism same package: typo3/cms
CVE-2020-8091 medium Typo3 Cross-Site Scripting in Flash component (ELTS) same package: typo3/cms
CVE-2018-14041 medium Bootstrap Cross-site Scripting vulnerability same package: typo3/cms
CVE-2019-11832 high TYPO3 Image Processing susceptible to Code Execution same package: typo3/cms