Insecure Unserialize in TYPO3 Backend

typo3/cms Updated 02 Oct 2025

Summary

05/06/2024
MODERATE
Yes i
Moderate
5.0

GHSA-c7rj-92xr-wprg: Insecure Unserialize in TYPO3 Backend. Affects typo3/cms across 3 version ranges.

>= 6.2.0, < 6.2.29 >= 7.6.0, < 7.6.13 >= 8.0.0, < 8.4.1

Fixed in 6.2.29, 7.6.13 or 8.4.1, depending on the release line you run. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Penetration testing for web, API and mobile Manual testing by engineers who build software, not an auditor's checklist. Trusted by teams at Swift and Google Talk to Devnack

Background

TYPO3 CMS is an open-source content management system that allows users to create and manage websites. It provides a backend interface for administrators to perform various tasks such as content editing, user management, and system configuration. However, a vulnerability has been discovered in the TYPO3 backend that can be exploited through insecure unserialize operations. This vulnerability requires a valid backend user account to exploit.

Vulnerability Detail

The suggest wizard in TYPO3 backend fails to properly validate incoming data, making it susceptible to insecure unserialize operations. This vulnerability can be exploited by an attacker with a valid backend user account. By crafting malicious serialized data, an attacker can execute arbitrary code or perform unauthorized actions within the TYPO3 backend. The impact of this vulnerability can range from unauthorized access to sensitive information to complete compromise of the TYPO3 installation.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 6.2.0, < 6.2.29 6.2.29
    composer require typo3/cms:6.2.29
  • >= 7.6.0, < 7.6.13 7.6.13
    composer require typo3/cms:7.6.13
  • >= 8.0.0, < 8.4.1 8.4.1
    composer require typo3/cms:8.4.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Workaround

There is no known workaround for this vulnerability. It is crucial to update TYPO3 CMS to the fixed versions mentioned above to mitigate the risk of exploitation.

Conclusion

Insecure unserialize vulnerability in the TYPO3 backend can lead to unauthorized access, information disclosure, and potential compromise of the entire TYPO3 installation. It is highly recommended to update TYPO3 CMS to the fixed versions mentioned above to mitigate the risk. For further support and assistance in vulnerability remediation, please contact DevNack.com.

See every vulnerability recorded for typo3/cms →

Share this vulnerability

FAQ

TYPO3 CMS is an open-source content management system used for creating and managing websites.

The suggest wizard is a feature in the TYPO3 backend that provides suggestions or autocomplete functionality for certain fields, making it easier for administrators to input data.

An attacker with a valid backend user account can exploit this vulnerability by crafting malicious serialized data and submitting it through the suggest wizard. When the backend processes the data, the insecure unserialize operation can be triggered, allowing the attacker to execute arbitrary code or perform unauthorized actions.

The consequences of this vulnerability can vary depending on the attacker's intentions. They can range from unauthorized access to sensitive information within the TYPO3 backend to complete compromise of the TYPO3 installation, allowing the attacker to take control of the website and perform malicious activities.

To protect your TYPO3 installation, it is crucial to update TYPO3 CMS to the fixed versions mentioned above. Regularly applying security updates and following best practices for secure configuration can also help mitigate the risk of exploitation.

References

Related vulnerabilities

Recent vulnerabilities recorded for typo3/cms.

How To Fix

Fixed versions by release line

The minimum fixed version depends on the release line you run.

  • >= 6.2.0, < 6.2.29 6.2.29
    composer require typo3/cms:6.2.29
  • >= 7.6.0, < 7.6.13 7.6.13
    composer require typo3/cms:7.6.13
  • >= 8.0.0, < 8.4.1 8.4.1
    composer require typo3/cms:8.4.1

Tip — Not sure which release line you're on? Vulert can find the fix for the version you are using. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback