Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-c78m-c52x-jgwp | TYPO3 CMS has Insecure Deserialization via Core API |
Tue, 09 Jun 2026 14:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 09 Jun 2026 11:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | TYPO3's cache frontend (VariableFrontend) and persistent key-value store (Registry) deserialized PHP payloads without integrity validation or class restrictions. An attacker with write access to the underlying storage backend (cache store or sys_registry database table) could inject a crafted serialized payload to trigger PHP Object Injection, potentially exploiting a gadget chain to achieve Remote Code Execution or other high-impact effects. Exploiting this vulnerability requires direct local write access to the storage, such as the SQL database or file system. This issue 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. | |
| Title | TYPO3 CMS - Insecure Deserialization in Core API | |
| First Time appeared |
Typo3
Typo3 typo3 |
|
| Weaknesses | CWE-502 | |
| CPEs | cpe:2.3:a:typo3:typo3:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Typo3
Typo3 typo3 |
|
| References |
| |
| Metrics |
cvssV4_0
|
Status: PUBLISHED
Assigner: TYPO3
Published:
Updated: 2026-06-09T13:40:40.839Z
Reserved: 2026-06-01T10:52:50.597Z
Link: CVE-2026-49740
Updated: 2026-06-09T13:40:37.814Z
Status : Deferred
Published: 2026-06-09T11:16:53.380
Modified: 2026-06-09T13:46:50.540
Link: CVE-2026-49740
No data.
OpenCVE Enrichment
Updated: 2026-06-09T20:15:06Z
Github GHSA