CVE-2026-49740: CWE-502 Deserialization of Untrusted Data in TYPO3 TYPO3 CMS
TYPO3 CMS contains a deserialization vulnerability in its cache frontend and persistent key-value store components. The vulnerability allows deserialization of untrusted PHP payloads without integrity checks or class restrictions. An attacker with local write access to the storage backend could inject malicious serialized data, potentially leading to PHP Object Injection and remote code execution. This affects multiple TYPO3 CMS versions prior to specified fixed releases. The vulnerability has a medium severity score of 6. 3 CVSS 4. 0.
AI Analysis
Technical Summary
TYPO3 CMS's VariableFrontend cache and Registry persistent key-value store deserialize PHP payloads without validating integrity or restricting classes. This allows an attacker with write access to the underlying storage (cache or sys_registry database table) to inject crafted serialized payloads. Exploitation could trigger PHP Object Injection and potentially remote code execution via gadget chains. The vulnerability affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.51, 12.0.0-12.4.46, 13.0.0-13.4.31, and 14.0.0-14.3.3. Exploitation requires local write access to the storage backend, such as the SQL database or filesystem.
Potential Impact
An attacker with write access to TYPO3 CMS's cache or sys_registry storage backend can inject malicious serialized PHP payloads. This can lead to PHP Object Injection, which may be leveraged to execute arbitrary code remotely or cause other high-impact effects. The vulnerability requires local write access, limiting remote exploitation scenarios. The CVSS 4.0 score is 6.3 (medium severity), reflecting the need for local privileges and the potential for significant impact if exploited.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch links are provided, users should monitor TYPO3 vendor advisories for updates. Mitigation involves restricting write access to the cache storage backend and sys_registry database table to trusted users only. Avoid allowing untrusted users to write serialized data to these storage locations. Apply any official patches once available.
CVE-2026-49740: CWE-502 Deserialization of Untrusted Data in TYPO3 TYPO3 CMS
Description
TYPO3 CMS contains a deserialization vulnerability in its cache frontend and persistent key-value store components. The vulnerability allows deserialization of untrusted PHP payloads without integrity checks or class restrictions. An attacker with local write access to the storage backend could inject malicious serialized data, potentially leading to PHP Object Injection and remote code execution. This affects multiple TYPO3 CMS versions prior to specified fixed releases. The vulnerability has a medium severity score of 6. 3 CVSS 4. 0.
CVSS v4.0
Score 6.3medium
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
TYPO3 CMS's VariableFrontend cache and Registry persistent key-value store deserialize PHP payloads without validating integrity or restricting classes. This allows an attacker with write access to the underlying storage (cache or sys_registry database table) to inject crafted serialized payloads. Exploitation could trigger PHP Object Injection and potentially remote code execution via gadget chains. The vulnerability affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.51, 12.0.0-12.4.46, 13.0.0-13.4.31, and 14.0.0-14.3.3. Exploitation requires local write access to the storage backend, such as the SQL database or filesystem.
Potential Impact
An attacker with write access to TYPO3 CMS's cache or sys_registry storage backend can inject malicious serialized PHP payloads. This can lead to PHP Object Injection, which may be leveraged to execute arbitrary code remotely or cause other high-impact effects. The vulnerability requires local write access, limiting remote exploitation scenarios. The CVSS 4.0 score is 6.3 (medium severity), reflecting the need for local privileges and the potential for significant impact if exploited.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Since no official fix or patch links are provided, users should monitor TYPO3 vendor advisories for updates. Mitigation involves restricting write access to the cache storage backend and sys_registry database table to trusted users only. Avoid allowing untrusted users to write serialized data to these storage locations. Apply any official patches once available.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- TYPO3
- Date Reserved
- 2026-06-01T10:52:50.597Z
- Cvss Version
- 4.0
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a27f8418dd33fbd8526d9e4
Added to database: 6/9/2026, 11:25:53 AM
Last enriched: 6/9/2026, 11:41:13 AM
Last updated: 6/9/2026, 2:45:06 PM
Views: 7
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.