Summary
Ein entfernter, authentisierter Angreifer kann mehrere Schwachstellen in TYPO3 Core ausnutzen, um Sicherheitsbeschränkungen zu umgehen, Benutzer auf schädliche Websites umzuleiten, beliebigen Code auszuführen, Berechtigungen zu eskalieren oder andere Auswirkungen zu verursachen.
Product
TYPO3 ist ein freies Content-Management-System, basierend auf der Scriptsprache PHP und einer SQL-Datenbank. Über zahlreiche Extensions kann der Funktionsumfang der Core-Installation individuell erweitert werden.
Vulnerabilities 15
-
High 8.7
TYPO3 CMS - Privilege Escalation & SQL Injection in Form Framework
Backend users with write access to the form_definition database table were able to directly create, update, or delete form definition records via DataHandler, bypassing the Form Framework's persistence validation and permission checks. This allowed injecting …
-
High 7.6
TYPO3 CMS - Broken Access Control in Form Framework
Backend users with access to the Form Framework were able to use files not ending in .form.yaml as form definitions, which were processed without denying the incorrect file extension. Maliciously crafted form definition files can be used to execute arbitrary …
-
High 7.6
TYPO3 CMS - Broken Access Control in Form Framework
Backend users with file write permissions were able to upload form definition files with mixed-case extensions (e.g., .FORM.YAML) to bypass the Form Framework's upload restriction. Maliciously crafted form definition files can be used to execute arbitrary SQL…
-
High 7.2
TYPO3 CMS - Destructive Actions on File Mount Folders
Non-privileged backend users with file mount access were able to perform write operations (move, delete, rename) on folders representing the root of an active file mount due to missing authorization restrictions. This issue affects TYPO3 CMS versions before 1…
-
High 7.1
TYPO3 CMS - Broken Access Control in Media Module
Backend users with file download permissions were able to download files from the fallback storage of the file abstraction layer (FAL) via the Media Module. Since the fallback storage resolves paths relative to the server's document root, this could expose se…
-
Medium 6.3
TYPO3 CMS - Insecure Deserialization in Core API
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 data…
-
Medium 5.3
TYPO3 CMS - Open Redirect in Core Utilities
Applications that use GeneralUtility::sanitizeLocalUrl to allow only local URLs are vulnerable to open redirect attacks if the URL is used after it has passed the aforementioned sanitization checks. This enables attackers to redirect users to external content…
-
Medium 5.3
TYPO3 CMS - Broken Access Control in Recycler
Backend users with access to the Recycler module were able to restore soft-deleted records on pages or for tables they were not authorized to modify. This issue affects TYPO3 CMS versions before 10.4.57, 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0…
-
Medium 5.3
TYPO3 CMS - Broken Access Control in DataHandler
Backend users were able to move records to a different page without having edit permissions on the source page. This issue affects TYPO3 CMS versions 13.0.0-13.4.30 and 14.0.0-14.3.2.
-
Medium 5.3
TYPO3 CMS - Broken Access Control in Clipboard
Backend users were able to insert arbitrary records and files into the TYPO3 clipboard without proper read permission checks, which allowed users to gather information about records and files they were not authorized to view. This issue affects TYPO3 CMS vers…
-
Medium 5.3
TYPO3 CMS - Broken Access Control in Backend API
Authenticated backend users were able to retrieve file metadata via several Backend API routes without proper permission checks, allowing access to files outside their permitted file mounts or storages. This issue affects TYPO3 CMS versions before 10.4.57, 11…
-
Medium 5.1
TYPO3 HTML Sanitizer allows Cross-Site Scripting
Namespace attributes are not encoded correctly during HTML serialization. This allows bypassing the cross-site scripting prevention mechanism of typo3/html-sanitizer before version 2.3.2.
-
Medium 5.1
TYPO3 CMS - Cross-Site Scripting in Indexed Search
Editors with access to create or modify page content were able to include HTML markup in page titles that were stored in the search index without sanitization. When displayed in frontend search results via the Indexed Search plugin, these titles were rendered…
-
Low 2.1
TYPO3 HTML Sanitizer allows Cross-Site Scripting
When ALLOW_INSECURE_RAW_TEXT is enabled, whitespace-variant closing tags (e.g., </style\t>) are not recognized by the sanitizer but accepted by browsers as valid end tags, allowing subsequent content to escape sanitization. This allows bypassing the cross-sit…
-
Low 2.1
TYPO3 CMS - Broken Access Control in File Abstraction Layer
The path allowance check in GeneralUtility::isAllowedAbsPath() performed a plain string prefix comparison without requiring a directory separator boundary, causing a path like /var/www/html-other/secret.yaml to be incorrectly accepted as valid when the projec…
Revision history
-
#2
Referenz(en) aufgenommen: CVE-2026-47351, EUVD-2026-35398, EUVD-2026-35396, EUVD-2026-35395, EUVD-2026-35394, EUVD-2026-35393, EUVD-2026-35392, EUVD-2026-35391, EUVD-2026-35403, EUVD-2026-35402, EUVD-2026-35400, EUVD-2026-35399, EUVD-2026-35397, EUVD-2026-35401
-
#1
Initiale Fassung
References
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-006 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-006
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-007 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-007
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-008 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-008
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-009 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-009
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-010 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-010
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-011 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-011
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-012 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-012
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-013 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-013
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-014 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-014
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-015 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-015
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-016 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-016
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-018 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-018
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-019 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-019
-
Typo3 Core Security Advisory TYPO3-CORE-SA-2026-017 vom 2026-06-08
https://typo3.org/security/advisory/typo3-core-sa-2026-017