TYPO3
Don't miss out!
Thousands of developers use stack.watch to stay informed.Get an email whenever new security vulnerabilities are reported in TYPO3.
TYPO3 EOL Dates
Ensure that you are using a supported version of TYPO3. Here are some end of life, and end of support dates for TYPO3.
| Release | EOL | End of Support | End of Extended Support | Status |
|---|---|---|---|---|
| 14 | June 30, 2029 | December 31, 2027 | June 30, 2032 |
Active
TYPO3 14 will become EOL in 3 years (in 2029). |
| 13 | December 31, 2027 | June 30, 2026 | December 31, 2030 |
Active
TYPO3 13 will become EOL next year, in December 2027. |
| 12 | April 30, 2026 | October 31, 2024 | April 30, 2029 |
EOL
TYPO3 12 became EOL in 2026 and the extended support period ends in 2029. |
| 11 | October 31, 2024 | March 31, 2023 | October 31, 2027 |
EOL
TYPO3 11 became EOL in 2024 and the extended support period ends in 2027. |
| 10 | April 30, 2023 | October 31, 2021 | April 30, 2026 |
EOL
TYPO3 10 became EOL in 2023 and the extended support period ended in 2026. |
| 9 | September 30, 2021 | April 30, 2020 | September 30, 2024 |
EOL
TYPO3 9 became EOL in 2021 and the extended support period ended in 2024. |
| 8 | March 31, 2020 | September 30, 2018 | March 31, 2024 |
EOL
TYPO3 8 became EOL in 2020 and the extended support period ended in 2024. |
| 7 | December 1, 2018 | April 1, 2017 | November 30, 2022 |
EOL
TYPO3 7 became EOL in 2018 and the extended support period ended in 2022. |
Extended Support differs by vendor, and may cost additional fees. Check with TYPO3 to see how they define extended support.
By the Year
In 2026 there have been 45 vulnerabilities in TYPO3 with an average score of 6.7 out of ten. Last year, in 2025 TYPO3 had 6 security vulnerabilities published. That is, 39 more vulnerabilities have already been reported in 2026 as compared to last year.
| Year | Vulnerabilities | Average Score |
|---|---|---|
| 2026 | 45 | 6.72 |
| 2025 | 6 | 0.00 |
| 2024 | 9 | 5.64 |
| 2023 | 6 | 5.52 |
| 2022 | 15 | 6.11 |
| 2021 | 16 | 6.37 |
| 2020 | 13 | 6.69 |
| 2019 | 6 | 7.50 |
| 2018 | 1 | 0.00 |
It may take a day or so for new TYPO3 vulnerabilities to show up in the stats or in the list of recent security vulnerabilities. Additionally vulnerabilities may be tagged under a different product or component name.
Recent TYPO3 Security Vulnerabilities
TYPO3 RSS Widget SSRF via Unrestricted URL Fetch
CVE-2026-125165
5.3 - Medium
- November 17, 2026
The RSS widget of the dashboard allows backend users to configure the URL of the RSS feed in the widget settings. The URL was fetched by the server without restricting the target host. Backend users with access to the dashboard could therefore make the server send HTTP requests to arbitrary hosts, including internal network services and cloud metadata endpoints, which are not reachable from the outside.
SSRF
TYPO3 File Dump eID Token Bypass Allows Unauthorized File Access
CVE-2026-125164
6.3 - Medium
- November 17, 2026
The file dump controller (eID=dumpFile) delivers files, file references and processed files identified by their uid, protected by a token. The token only covered the uid value, but not the type of the requested resource. A valid token issued for a file could therefore be reused to request a file reference or a processed file with the same uid. As a result, unauthenticated visitors could download files, for example from non-public storages, for which no token had been issued.
Insecure Direct Object Reference / IDOR
TYPO3 Form Framework FileUpload allowedMimeTypes bypass XSS
CVE-2026-125163
6.3 - Medium
- November 17, 2026
The FileUpload and ImageUpload elements of the Form Framework use the property allowedMimeTypes as an allow list of MIME types accepted for upload. An empty allowedMimeTypes list was treated as "no restriction". Forms containing upload elements without any configured MIME type, for example in manually created form definitions or when all MIME types were deselected in the form editor, accepted any file except those blocked by the file deny pattern, which only covers PHP-related file extensions. This allowed unauthenticated users to upload files with browser-executable content, such as HTML or SVG documents, to the configured upload folder, which by default is located in a public storage. If attackers know the URL of an uploaded file (see TYPO3-CORE-SA-2026-029), this could lead to Cross-Site Scripting on web servers that do not apply the Content-Security-Policy recommended by TYPO3 to the form upload target folder.
Unrestricted File Upload
TYPO3 cHash array handling leads to cache exhaustion (CVE-2026-125162)
CVE-2026-125162
8.2 - High
- November 17, 2026
The cHash argument, which ensures that only URL arguments originally generated by TYPO3 create separate page cache entries, was treated inconsistently when it was passed as an array. The cHash validation treated such a value as missing, while the page cache identifier treated it as present and included all URL arguments. As a result, unauthenticated visitors could create an unlimited number of page cache entries and trigger uncached page renderings by adding an array cHash with arbitrary values to any URL. This could exhaust server resources and fill the page cache storage. Only installations where the cHash validation is not enforced via $GLOBALS['TYPO3_CONF_VARS']['FE']['cacheHash']['enforceValidation'] are affected. This setting is enabled by default for new installations since TYPO3 v12, but is often still disabled in installations upgraded from older versions.
Allocation of Resources Without Limits or Throttling
TYPO3 PHP Open Redirect via sanitizeLocalUrl Improper URL Handling
CVE-2026-125161
5.3 - Medium
- November 17, 2026
The fix for TYPO3-CORE-SA-2026-009 was incomplete. GeneralUtility::sanitizeLocalUrl performed its checks on the URL-decoded value, but returned the original, URL-encoded value. URLs containing certain percent-encoded characters therefore passed the sanitization checks as local URLs, although they point to an external host. Applications that use the sanitized URL for redirects are vulnerable to open redirect attacks. This enables attackers to redirect users to external content and carry out phishing attacks. In the TYPO3 core, this affects redirects in the backend, which require the victim to be logged in to the backend.
Open Redirect
TYPO3 Form FileUpload Path Disclosure & XSS via error msgs
CVE-2026-125160
6.3 - Medium
- November 17, 2026
Files uploaded through FileUpload or ImageUpload elements are stored in an unguessable sub-folder that remains the same for the whole form session. If storing an uploaded file failed, for example because of a file name exceeding the file system's length limit, the raw error message was shown to the frontend user disclosing the storage path including the unguessable folder name and the server's temporary upload directory. With this information, attackers could determine the public URL of files they upload through the form. If a form allows uploading files that browsers can execute, such as HTML documents, this could lead to Cross-Site Scripting on web servers that do not apply the Content-Security-Policy recommended by TYPO3 to the form upload target folder. This vulnerability is known to be actively exploited.
Generation of Error Message Containing Sensitive Information
TYPO3 Image Upload Path Disclosure via ImageMagick MVG Coder
CVE-2026-125159
8.2 - High
- November 17, 2026
ImageMagick and GraphicsMagick use small modules, called "coders", to read each image format. When processing images, TYPO3 determined the coder from the file type detected by the file contents, as long as the detected mime-type started with image/. A file containing MVG (Magick Vector Graphics) instructions, uploaded with an image file extension like .png, was therefore processed with the MVG coder. MVG instructions can read local files into the processed image, which allows disclosing the contents of arbitrary files readable by the web server, for example configuration files containing credentials, through a publicly accessible processed image. Exploiting this vulnerability requires a way to upload files without a mime-type check, for example a public form of the Form Framework using a FileUpload or ImageUpload element without configured allowedMimeTypes (see TYPO3-CORE-SA-2026-032), which allows exploitation by unauthenticated visitors. Additionally, ImageMagick must be used for image processing, and its default system configuration must allow the MVG coder.
Denylist / Deny List
TYPO3 CMS Installer Reenable via FIRST_INSTALL Marker Leads to RCE
CVE-2026-119623
9.4 - Critical
- November 17, 2026
The installer (first installation wizard) could be re-enabled on an already configured instance by placing a file whose name starts with FIRST_INSTALL in the public web root or the project root. The installer then became accessible without authentication, allowing for example to change the database connection and to create a new administrator and system maintainer account, which leads to remote code execution. As demonstrated in TYPO3-CORE-SA-2026-026, such a file could be created by an authenticated, low-privileged backend user without any further permissions. Other ways of creating files in the web root, as well as leftover or restored marker files, could be abused in the same way. With the fixed versions, the installer can no longer be re-enabled on an already configured instance by a marker file. A new internal setting $GLOBALS['TYPO3_CONF_VARS']['SYS']['isInstalling'] is stored in the system configuration and is only enabled while a new installation is running. Additionally, only the exact file names FIRST_INSTALL and FIRST_INSTALL.txt are accepted as marker files.
Missing Authentication for Critical Function
TYPO3 Media Upload Path Traversal & Installer Reenable RCE
CVE-2026-119622
7.1 - High
- November 17, 2026
The backend endpoint for adding online media (e.g. YouTube or Vimeo videos) accepted a target folder in the fallback storage (storage uid 0), which points to the public web root of the installation. File mount and permission checks are not applied to the fallback storage. As a result, any authenticated, low-privileged backend user, even without file mounts or module access, could create online media files with a partially controllable file name in the public web root. In combination with TYPO3-CORE-SA-2026-027, this could be used to re-enable the installer on an already configured instance. The installer could then be used to create a new administrator and system maintainer account, which leads to remote code execution.
AuthZ
TYPO3 Import/Export Arbitrary File Write RCE via Unvalidated Hash
CVE-2026-119621
7.7 - High
- November 17, 2026
When importing a T3D or XML file in the Import/Export module, the file hash values of imported files were taken from the import data without validation and used to build the path of a temporary file. A crafted import file could therefore write files with arbitrary content to any location writable by the web server, for example a PHP file in the public web root, which leads to remote code execution. Exploiting this vulnerability requires an administrator backend user account, or a non-admin backend user for whom importing has been enabled via the user TSconfig option options.impexp.enableImportForNonAdminUser.
Directory traversal
TYPO3 Predictable Download Token Leads to Unauth File Access
CVE-2026-112240
6.3 - Medium
- October 20, 2026
The download link for files uploaded through a form relied on a token that could be predicted. The file name in the request was also not verified in a way that resisted guessing. An unauthenticated attacker could use this to access files uploaded by other visitors. In addition, the token was shown in plain text in the text version of the notification email.
Insecure Direct Object Reference / IDOR
TYPO3 CMS Email HTML Injection (XSS)
CVE-2026-113442
5.3 - Medium
- October 20, 2026
Values entered by visitors were placed into the HTML summary email without being escaped. An unauthenticated attacker could use this to inject HTML into an email that is shown to the recipient.
XSS
TYPO3 CMS Order Plugin Insecure Ownership Checks (CVE-2026-112071)
CVE-2026-112071
6.9 - Medium
- October 20, 2026
The order cancellation function accepts an order identifier from the request and acts on that order without checking that the caller owns it. Any site visitor can set orders that are still awaiting payment to "canceled". This requires a page that contains the shop's order plugin. Orders that are already paid are not affected.
AuthZ
IPN verification flaw in TYPO3 ecommerce plugin allows order tampering
CVE-2026-113468
6.9 - Medium
- October 20, 2026
The payment notification endpoint for PayPal accepts incoming data without verifying that it comes from the payment provider. Any site visitor can overwrite the stored payment notification of an order that is still awaiting payment with arbitrary content. This requires a page that contains the shop's order plugin. Orders that are already paid are not affected.
AuthZ
TYPO3 CMS Backend Endpoint Unchecked Page Field Update Leads to PrivEsc
CVE-2026-112239
7.2 - High
- October 20, 2026
The extension provides a backend endpoint that writes a submitted value into a submitted field of a submitted page record. It neither checks the user's permissions nor limits which fields can be changed. Any authenticated backend user can therefore change any property of any page, including its access permissions and configuration, outside the scope granted to them.
AuthZ
TYPO3 CMS OpenAI API Key Exposure in Backend Plugin
CVE-2026-113459
7.1 - High
- October 20, 2026
In versions running on TYPO3 10 and 11, the configured OpenAI API key is embedded in every backend page, so that the editor plugin can contact the OpenAI service directly from the browser. Any authenticated backend user can read the key and use it at the expense of the site operator. This only applies if an API key has been configured.
Insertion of Sensitive Information Into Sent Data
TYPO3 CMS Auth Bypass in Localization Wizard AJAX Routes (v10-14)
CVE-2026-77132
5.3 - Medium
- September 08, 2026
It has been discovered that several AJAX routes used for the backend localization wizard failed to perform authorization checks. This allowed authenticated, low-privileged backend users to access information about records and content elements that fall outside of their permitted range. Exploiting this vulnerability requires a low-privileged backend user account. This issue affects TYPO3 CMS versions 10.0.0-10.4.59, 11.0.0-11.5.53, 12.0.0-12.4.48, 13.0.0-13.4.34 and 14.0.0-14.3.6.
AuthZ
TYPO3 CMS 14.2-14.3: Admin Priv escalation via config cmds
CVE-2026-85400
7.5 - High
- September 08, 2026
Backend administrators without system maintainer privileges were able to schedule any of the configuration:read, configuration:set, and configuration:show commands. This allowed them to modify arbitrary system configuration, which is normally limited to system maintainers. As a consequence, this allowed them, for example, to gain system maintainer privileges or cause a denial of service. Exploiting this vulnerability requires an administrator-level backend user account. This issue affects TYPO3 CMS versions 14.2.0-14.3.6.
AuthZ
TYPO3 CMS Extension Bypasses Subpage Access via Cached Rootline
CVE-2026-56092
7.6 - High
- August 25, 2026
The extension forces empty frontend-group and subpage-inheritance restrictions onto page records during indexer sub-requests, and this forged state was persisted into the shared rootline cache, allowing anonymous visitors to bypass extendToSubpages-inherited access restrictions on cached pages.
AuthZ
TYPO3 solr Extension Frontend Detail-View Bypass: SiteHash & FE Filters Not Applied
CVE-2026-56093
6.3 - Medium
- August 25, 2026
The extension's frontend detail-view document lookup does not apply the current site's siteHash filter or frontend user access filter, unlike the regular search path. A visitor who can obtain or guess a valid Solr document id can retrieve documents through this lookup without the same access restrictions enforced elsewhere.
Insecure Direct Object Reference / IDOR
TYPO3 Solr Ext: Unchecked Filter Injection Enables Site Hash Bypass
CVE-2026-56094
6.3 - Medium
- August 25, 2026
The extension allows a request-provided additionalFilters parameter to register a named siteHash filter before the system's own siteHash filter is applied, and the query builder does not overwrite an already-registered named filter. In a shared Solr core serving multiple TYPO3 sites, a visitor can use this to read public documents belonging to another site. The same root cause also affects the suggest top-results path when suggest is enabled.
Improper Neutralization of Special Elements in Data Query Logic
TYPO3 PHP Object Injection via Unserialize in Indexer
CVE-2026-56095
7.7 - High
- August 25, 2026
The extension's indexer passed every field value returned by content object rendering through PHP's unserialize() function when transferring multi-value data for the SOLR_CLASSIFICATION, SOLR_MULTIVALUE and SOLR_RELATION content object types, rather than a safe format. If user-generated content saved in the TYPO3 database can reach an indexed field, this exposes a PHP Object Injection surface.
Marshaling, Unmarshaling
TYPO3 Extension: Unrestricted Solr Query Injection Enables Blind Data Extraction
CVE-2026-56096
6.3 - Medium
- August 25, 2026
The extension passes the user-supplied search query parameter to Apache Solr without restricting advanced Solr query syntax such as wildcards, field selectors and range queries. A remote, unauthenticated attacker can use this syntax to enumerate indexed field names and extract their stored values through boolean- and range-based blind extraction techniques, independent of any site-specific configuration.
Improper Neutralization of Special Elements in Data Query Logic
TYPO3 CMS Extension Sends System Info in Cleartext Without OpenSSL
CVE-2026-77131
5.3 - Medium
- August 25, 2026
When OpenSSL is unavailable on the server, the extension transmits TYPO3 system information in cleartext instead of encrypting it. Exploitation requires the attacker to already be in control of the SYSSY project's API key.
Cleartext Transmission of Sensitive Information
TYPO3 SysSy JWT Expiration Validation Bypass
CVE-2026-77130
5.3 - Medium
- August 25, 2026
The extension fails to properly validate the expiration of a client-supplied JWT token, allowing an attacker in control of a valid API key to authenticate with an expired token. Exploitation requires the attacker to already be in control of the SYSSY project's API key.
Insufficient Session Expiration
TYPO3 CMS 13-14 Referrer Bypass Enables Backend Access via SameDomain JS
CVE-2026-19418
7.3 - High
- August 11, 2026
The referrer enforcement introduced with TYPO3-CORE-SA-2020-006 (CVE-2020-11069) became ineffective in TYPO3 v13.0, where TYPO3 CMS started serving the backend and Install Tool applications from the site's main entry script instead of the dedicated typo3/ directory. Whether a request originated from the backend or Install Tool itself was determined by comparing the referrer against the directory of the entry script, which since then is the site root. As a consequence, requests originating from any script running on one of the TYPO3 instance's own domains, such as a frontend page, were accepted by backend routes and Install Tool endpoints. Attackers able to execute JavaScript on one of those domains, for instance by exploiting a cross-site scripting vulnerability, could invoke these endpoints via Fetch/XHR with the privileges of an authenticated victim's user session. This issue affects TYPO3 CMS versions 13.0.0-13.4.33 and 14.0.0-14.3.5.
Origin Validation Error
TYPO3 CMS 14.2-14.3.5: Arbitrary MIME type upload
CVE-2026-15305
- July 14, 2026
Users were able to upload files with arbitrary MIME types to forms using FileUpload or ImageUpload elements with allowedMimeTypes configured. The restriction was not enforced server-side because the MimeTypeValidator was registered during form building before concrete form definition properties were applied, resulting in the validator never being added to the processing pipeline. This issue affects TYPO3 CMS versions 14.2.0-14.3.4.
Insufficient Type Distinction
TYPO3 CMS FAL Media Module file download flaw (v1114)
CVE-2026-49742
- June 09, 2026
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 sensitive files such as log files. This issue affects TYPO3 CMS versions 11.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.
Directory traversal
TYPO3 CMS 14.014.3.3 FormFramework DataHandler Bypass
CVE-2026-49741
- June 09, 2026
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 arbitrary form configurations, re-enabling attack vectors originally addressed in TYPO3-CORE-SA-2018-003, including SQL injection and privilege escalation. This issue affects TYPO3 CMS versions 14.0.0-14.3.2.
AuthZ
TYPO3 CMS PHP Object Injection via VarFront/Reg deserialization (v<14)
CVE-2026-49740
- June 09, 2026
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.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.
Marshaling, Unmarshaling
TYPO3 CMS Path Traversal in GeneralUtility::isAllowedAbsPath < 14.3.3
CVE-2026-49738
- June 09, 2026
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 project root was /var/www/html. Administrator users with access to the File Abstraction Layer were able to create new file storage definitions pointing to directories outside the project root, bypassing this path check. 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.0-14.3.2.
Directory traversal
TYPO3 CMS File Meta Disclosure via Backend API < 10.4.57
CVE-2026-47352
- June 09, 2026
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.0.0-11.5.50, 12.0.0-12.4.45, 13.0.0-13.4.30 and 14.0.0-14.3.2.
AuthZ
TYPO3 CMS clipboard privilege escalation in v10.4-14.3
CVE-2026-47351
- June 09, 2026
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 versions 10.4.0-13.4.30 and 14.0.0-14.3.2.
AuthZ
TYPO3 CMS <=14.3.3 Auth Bypass: Move records w/o edit perms.
CVE-2026-47350
- June 09, 2026
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.
AuthZ
TYPO3 CMS Soft-Delete Restore Exploit in 10.4.57/11.5.51/12.4.46/13.4.31/14.3.3
CVE-2026-47349
- June 09, 2026
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.0-14.3.2.
AuthZ
TYPO3 CMS 13-14 XSS via Unsanitized Page Titles in Indexed Search Plugin
CVE-2026-47348
- June 09, 2026
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 without proper output encoding, resulting in a Cross-Site Scripting vulnerability. This issue affects TYPO3 CMS versions 13.0.0-13.4.30 and 14.0.0-14.3.2.
XSS
TYPO3 CMS Open Redirect via GeneralUtility::sanitizeLocalUrl (v<10.4.57)
CVE-2026-47347
- June 09, 2026
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 and carry out phishing attacks. 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.0-14.3.2.
Open Redirect
TYPO3 CMS MixedCase File Upload SQLi ( 10.4.57/11.5.50/12.4.45/13.4.30/14.3.2)
CVE-2026-47346
- June 09, 2026
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 statements, allowing attackers to escalate privileges by creating administrative backend user accounts. 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.0-14.3.2.
Improper Handling of Case Sensitivity
TYPO3 CMS <10.4.57/11-11.5.50/12-12.4.45/13-13.4.30/14-14.3.2: File Mount Auth Bypass
CVE-2026-47343
- June 09, 2026
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 10.4.57, 11.0.0 through 11.5.50, 12.0.0 through 12.4.45, 13.0.0 through 13.4.30, and 14.0.0 through 14.3.2.
AuthZ
TYPO3 CMS 14.3.3 Form Framework SQLi via .form.yaml Bypass
CVE-2026-11607
- June 09, 2026
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 SQL statements, allowing attackers to escalate privileges by creating administrative backend user accounts. 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.0-14.3.2.
AuthZ
TYPO3 CMS 14.2.0: Backend password change stores cleartext in uc/user_settings
CVE-2026-6553
- April 21, 2026
Changing backend users' passwords via the user settings module results in storing the cleartext password in the uc and user_settings fields of the be_users database table. This issue affects TYPO3 CMS version 14.2.0.
Cleartext Storage of Sensitive Information
TYPO3 CMS mailfile spool deserialization PHP RCE (v10-14)
CVE-2026-0859
- January 13, 2026
TYPO3's mailfile spool deserialization flaw lets local users with write access to the spool directory craft a malicious file that is deserialized during the mailer:spool:send command, enabling arbitrary PHP code execution on the web server. This issue affects TYPO3 CMS versions 10.0.0-10.4.54, 11.0.0-11.5.48, 12.0.0-12.4.40, 13.0.0-13.4.22 and 14.0.0-14.0.1.
Marshaling, Unmarshaling
TYPO3 CMS Arbitrary Data Deletion via Recycler (v10-14)
CVE-2025-59022
- January 13, 2026
Backend users who had access to the recycler module could delete arbitrary data from any database table defined in the TCA - regardless of whether they had permission to that particular table. This allowed attackers to purge and destroy critical site data, effectively rendering the website unavailable. This issue affects TYPO3 CMS versions 10.0.0-10.4.54, 11.0.0-11.5.48, 12.0.0-12.4.40, 13.0.0-13.4.22 and 14.0.0-14.0.1.
AuthZ
TYPO3 CMS Unrestricted Redirect Modification (10-14)
CVE-2025-59021
- January 13, 2026
Backend users with access to the redirects module and write permission on the sys_redirect table were able to read, create, and modify any redirect record without restriction to the users own file-mounts or web-mounts. This allowed attackers to insert or alter redirects pointing to arbitrary URLs facilitating phishing or other malicious redirect attacks. This issue affects TYPO3 CMS versions 10.0.0-10.4.54, 11.0.0-11.5.48, 12.0.0-12.4.40, 13.0.0-13.4.22 and 14.0.0-14.0.1.
AuthZ
Fieldlevel access bypass in TYPO3 CMS 10-14 via defVals param
CVE-2025-59020
- January 13, 2026
By exploiting the defVals parameter, attackers could bypass fieldlevel access checks during record creation in the TYPO3 backend. This gave them the ability to insert arbitrary data into prohibited exclude fields of a database table for which the user already has write permission for a reduced set of fields. This issue affects TYPO3 CMS versions 10.0.0-10.4.54, 11.0.0-11.5.48, 12.0.0-12.4.40, 13.0.0-13.4.22 and 14.0.0-14.0.1.
AuthZ
TYPO3 DBAL FrontendUser Permission Leak (9.0.0-13.4.12)
CVE-2025-47937
- May 20, 2025
TYPO3 is an open source, PHP based web content management system. Starting in version 9.0.0 and prior to versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, and 13.4.12 LTS, when performing a database query involving multiple tables through the database abstraction layer (DBAL), frontend user permissions are only applied via `FrontendGroupRestriction` to the first table. As a result, data from additional tables included in the same query may be unintentionally exposed to unauthorized users. Users should update to TYPO3 version 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS to fix the problem.
AuthZ
TYPO3 FileManager Upload: Upload any file type, vulnerable before v13.4.12
CVE-2025-47939
- May 20, 2025
TYPO3 is an open source, PHP based web content management system. By design, the file management module in TYPO3s backend user interface has historically allowed the upload of any file type, with the exception of those that are directly executable in a web server context. This lack of restriction means it is possible to upload files that may be considered potentially harmful, such as executable binaries (e.g., `.exe` files), or files with inconsistent file extensions and MIME types (for example, a file incorrectly named with a `.png` extension but actually carrying the MIME type `application/zip`) starting in version 9.0.0 and prior to versions 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, and 13.4.12 LTS. Although such files are not directly executable through the web server, their presence can introduce indirect risks. For example, third-party services such as antivirus scanners or malware detection systems might flag or block access to the website for end users if suspicious files are found. This could negatively affect the availability or reputation of the site. Users should update to TYPO3 version 9.5.51 ELTS, 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS to fix the problem.
Unrestricted File Upload
TYPO3 Admin Priv Esc via Backend User in 10.0.0-13.4.12 LTS
CVE-2025-47940
- May 20, 2025
TYPO3 is an open source, PHP based web content management system. Starting in version 10.0.0 and prior to versions 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, and 13.4.12 LTS, administrator-level backend users without system maintainer privileges can escalate their privileges and gain system maintainer access. Exploiting this vulnerability requires a valid administrator account. Users should update to TYPO3 version 10.4.50 ELTS, 11.5.44 ELTS, 12.4.31 LTS, or 13.4.12 LTS to fix the problem.
Unverified Ownership
TYPO3 <=11.5.41 CSRF via Deep Links & GET State Change
CVE-2024-55924
- January 14, 2025
TYPO3 is a free and open source Content Management Framework. A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method. Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions: The user opens a malicious link, such as one sent via email. The user visits a compromised or manipulated website while the following settings are misconfigured: 1. `security.backend.enforceReferrer` feature is disabled, 2. `BE/cookieSameSite` configuration is set to lax or none. The vulnerability in the affected downstream component Scheduler Module allows attackers to trigger pre-defined command classes - which can lead to unauthorized import or export of data in the worst case. Users are advised to update to TYPO3 versions 11.5.42 ELTS which fixes the problem described. There are no known workarounds for this vulnerability.
Session Riding
TYPO3 CSRF via Deep Links in Backend UI (Fixed in 13.4.3 LTS)
CVE-2024-55921
- January 14, 2025
TYPO3 is a free and open source Content Management Framework. A vulnerability has been identified in the backend user interface functionality involving deep links. Specifically, this functionality is susceptible to Cross-Site Request Forgery (CSRF). Additionally, state-changing actions in downstream components incorrectly accepted submissions via HTTP GET and did not enforce the appropriate HTTP method. Successful exploitation of this vulnerability requires the victim to have an active session on the backend user interface and to be deceived into interacting with a malicious URL targeting the backend, which can occur under the following conditions: The user opens a malicious link, such as one sent via email. The user visits a compromised or manipulated website while the following settings are misconfigured: 1. `security.backend.enforceReferrer` feature is disabled, 2. `BE/cookieSameSite` configuration is set to lax or none. The vulnerability in the affected downstream component Extension Manager Module allows attackers to retrieve and install 3rd party extensions from the TYPO3 Extension Repository - which can lead to remote code execution in the worst case. Users are advised to update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS which fix the problem described.
Session Riding