TYPO3 TYPO3 Enterprise CMS

Don't miss out!

Thousands of developers use stack.watch to stay informed.
Get an email whenever new security vulnerabilities are reported in any TYPO3 product.

RSS Feeds for TYPO3 security vulnerabilities

Create a CVE RSS feed including security vulnerabilities found in TYPO3 products with stack.watch. Just hit watch, then grab your custom RSS feed url.

Products by TYPO3 Sorted by Most Security Vulnerabilities since 2018

TYPO3120 vulnerabilities

TYPO3 Html Sanitizer6 vulnerabilities

TYPO3 Pharstreamwrapper2 vulnerabilities

TYPO3 Fluid1 vulnerability

TYPO3 Fluid Engine1 vulnerability

TYPO3 Form To Database1 vulnerability

TYPO3 Mediace1 vulnerability

TYPO3 Modules1 vulnerability

TYPO3 Svg Sanitizer1 vulnerability

Typo3 Cms1 vulnerability

By the Year

In 2026 there have been 98 vulnerabilities in TYPO3 with an average score of 6.9 out of ten. Last year, in 2025 TYPO3 had 10 security vulnerabilities published. That is, 88 more vulnerabilities have already been reported in 2026 as compared to last year.




Year Vulnerabilities Average Score
2026 98 6.85
2025 10 0.00
2024 9 5.64
2023 7 5.60
2022 17 6.11
2021 16 6.37
2020 16 6.77
2019 8 9.03
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

CVE Date Vulnerability Products
CVE-2026-125165 Nov 17, 2026
TYPO3 RSS Widget SSRF via Unrestricted URL Fetch 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.
TYPO3
CVE-2026-125164 Nov 17, 2026
TYPO3 File Dump eID Token Bypass Allows Unauthorized File Access 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.
TYPO3
CVE-2026-125163 Nov 17, 2026
TYPO3 Form Framework FileUpload allowedMimeTypes bypass XSS 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.
TYPO3
CVE-2026-125162 Nov 17, 2026
TYPO3 cHash array handling leads to cache exhaustion (CVE-2026-125162) 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.
TYPO3
CVE-2026-125161 Nov 17, 2026
TYPO3 PHP Open Redirect via sanitizeLocalUrl Improper URL Handling 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.
TYPO3
CVE-2026-125160 Nov 17, 2026
TYPO3 Form FileUpload Path Disclosure & XSS via error msgs 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.
TYPO3
CVE-2026-125159 Nov 17, 2026
TYPO3 Image Upload Path Disclosure via ImageMagick MVG Coder 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.
TYPO3
CVE-2026-119623 Nov 17, 2026
TYPO3 CMS Installer Reenable via FIRST_INSTALL Marker Leads to RCE 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.
TYPO3
CVE-2026-119622 Nov 17, 2026
TYPO3 Media Upload Path Traversal & Installer Reenable RCE 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.
TYPO3
CVE-2026-119621 Nov 17, 2026
TYPO3 Import/Export Arbitrary File Write RCE via Unvalidated Hash 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.
TYPO3
CVE-2026-120327 Nov 03, 2026
TYPO3 CMS: Remote Open Redirect via Click Tracking Middleware The click tracking middleware accepts an arbitrary target URL and redirects to it. Attackers can misuse links to the website to redirect users to external sites.
CVE-2026-120328 Nov 03, 2026
TYPO3 CMS ClickTracking Middleware Exposes Personal Data via Unvalidated Auth Code The click tracking middleware does not validate the authentication code of a recipient if the code is omitted. Unauthenticated attackers can retrieve personal data of newsletter recipients, which is inserted into links of sent mails.
CVE-2026-120329 Nov 03, 2026
TYPO3 Mail TSconfig Write-Through Exposes Arbitrary TSConfig Saving the configuration of the mail backend module writes submitted settings to the page TSconfig without restricting them to the configuration options of the module. Backend users with access to the mail module can write arbitrary page TSconfig.
CVE-2026-120330 Nov 03, 2026
TYPO3 Mail Module: Backend Access Bypass Exposes Recipient Data Backend actions and ajax routes of the mail module do not check whether the backend user has access to the page of the requested mail or recipient group. Backend users with access to the mail module can view, change, send and export mails and recipient groups outside their web mounts, including the personal data of recipients.
CVE-2026-120331 Nov 03, 2026
TYPO3 CMS SSRF via External URL Mail Content Content of external URL mails, their stylesheets and images to embed is fetched by the server without validating the target host. Backend users with access to the mail module can make the server send requests to hosts in the internal network.
CVE-2026-120333 Nov 03, 2026
TYPO3 CMS Authn Hash Bypass in Email Links Enables User Enumeration/Deletion The actions linked in the emails of the extension (e.g. to confirm a registration or the deletion of an account) do not reject requests with a missing or invalid hash. Instead, the frontend user given in the request is used. Unauthenticated attackers can therefore perform these actions for arbitrary active frontend users. This allows them to retrieve the email address or username of all frontend users and to delete arbitrary frontend user accounts.
CVE-2026-120332 Nov 03, 2026
TYPO3 Mail Module XSS via Unescaped HTML in Backend The HTML content of mails and tracked URLs are rendered unescaped in the backend module. Backend users with access to the mail module can inject arbitrary HTML and JavaScript, which is executed in the context of other backend users viewing the mail preview or report.
CVE-2026-112069 Oct 20, 2026
TYPO3 14.3 Extension File Storage Auth Bypass The extension no longer applied its access protection to files in file storages that use a non-default relative base path. These files were served directly by the web server, without any authentication or permission check. The issue is only exploitable when the extension is used on a website running TYPO3 14.3.
CVE-2026-112065 Oct 20, 2026
TYPO3 Consent History Endpoint Access Bypass The routes that provide consent history and statistics data did not check whether the backend user had access to the module or to the requested page. Any authenticated backend user, regardless of permissions, could therefore retrieve consent data of any site in the installation.
CVE-2026-112064 Oct 20, 2026
TYPO3 Consent History Backend SQLi via Unvalidated Sort/Group Params The backend module for reviewing the consent history accepted sorting, grouping and index options from the request and used them in a database query without validation. Only the filter conditions of that query were bound as parameters. A backend user with access to the history or statistics functions could use this to read arbitrary data from the database, including password hashes of backend and frontend users.
CVE-2026-112066 Oct 20, 2026
TYPO3 Cookie Consent JSON Import Bypass Allows Arbitrary Script Injection The JSON import of the cookie consent configuration did not respect the backend user's permissions. Non-admin backend users with access to the module could import a configuration that adds arbitrary scripts to the frontend of the website.
CVE-2026-112068 Oct 20, 2026
TYPO3 Backend Module Access Control Bypass The backend module does not check whether a backend user has access to the requested site. Users with access to the module can therefore open the analytics dashboard of any site.
CVE-2026-112067 Oct 20, 2026
TYPO3 CAPTCHA Extension Embeds Answer in Image Allowing Bypass The extension hides the correct answer to each CAPTCHA inside the image data of the CAPTCHA itself. Anyone who can request a CAPTCHA image can read the answer from it and submit it, so automated clients can pass the challenge. This applies to the default configuration, because the audio feature that causes the answer to be embedded is enabled by default. Forms that rely on the CAPTCHA as their only protection against automated submissions are exposed to abuse by bots.
CVE-2026-112237 Oct 20, 2026
TYPO3 Public Proxy Endpoint SSRF Due to Missing Auth Check The extension provides a public proxy endpoint that fetches a URL on behalf of the visitor. For one HTTP request method, the endpoint does not apply the authorization check that protects the other methods, so the URL it fetches is fully controlled by the requester. An unauthenticated attacker can make the server send requests to arbitrary internal or external hosts. The attacker receives the status code and selected response headers, which allows probing of internal hosts and ports. Response bodies are not disclosed.
CVE-2026-112240 Oct 20, 2026
TYPO3 Predictable Download Token Leads to Unauth File Access 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.
TYPO3
CVE-2026-113442 Oct 20, 2026
TYPO3 CMS Email HTML Injection (XSS) 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.
TYPO3
CVE-2026-112238 Oct 20, 2026
TYPO3 CMS SQLi via Unescaped Quotes in File Search The file search of the extension builds its database conditions by wrapping the search term in quotes itself. Only the wildcard characters of the LIKE operator are escaped, quote characters are not. A crafted search term can therefore leave the intended string value and change the database query. This allows an attacker to read data from the database. The issue affects every searched field.
CVE-2026-112071 Oct 20, 2026
TYPO3 CMS Order Plugin Insecure Ownership Checks (CVE-2026-112071) 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.
TYPO3
CVE-2026-113468 Oct 20, 2026
IPN verification flaw in TYPO3 ecommerce plugin allows order tampering 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.
TYPO3
CVE-2026-112239 Oct 20, 2026
TYPO3 CMS Backend Endpoint Unchecked Page Field Update Leads to PrivEsc 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.
TYPO3
CVE-2026-112070 Oct 20, 2026
TYPO3 CMS Analytics Ext AJAX Auth Bypass The AJAX routes of the extension do not check whether a backend user has access to the related module or dashboard widget. Any backend user can therefore retrieve analytics data of the sites they have page access to.
CVE-2026-113459 Oct 20, 2026
TYPO3 CMS OpenAI API Key Exposure in Backend Plugin 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.
TYPO3
CVE-2026-109162 Oct 13, 2026
TYPO3 CMS 14.0.0-14.3.8 FileUpload saves to public storage Forms using FileUpload or ImageUpload elements with a custom saveToFileMount configured stored uploaded files in the default storage folder 1:/user_upload/ instead of the configured destination. This could cause uploaded files to end up in a publicly accessible storage even though a restricted, non-public storage had been configured. Files stored this way are served directly, without the access checks applied to non-public storages. Forms that use the default value for saveToFileMount are not affected. This issue affects TYPO3 CMS versions 14.0.0-14.3.8.
Typo3 Cms
CVE-2023-50459 Sep 14, 2026
TYPO3 femanager 7.x <7.2.3 Access Control Bypass (Edit/Delete Frontend Users) An issue was discovered in the femanager extension 7.x before 7.2.3 for TYPO3. It fails to check access permissions for the edit user component. An authenticated frontend user can exploit this to either edit data of various frontend users or delete various frontend user accounts.
CVE-2023-45023 Sep 14, 2026
TYPO3 femanager 7 Insecure Access to Invitation (CVE-2023-45023) The femanager extension 7 before 7.2.2 for TYPO3 has Incorrect Access Control: it lacks a check for permissions for the invitation component.
CVE-2023-50462 Sep 14, 2026
TYPO3 content_consent 2.0.1 IDOR via Unverified Content Element ID An issue was discovered in the content_consent (aka Content Consent) extension through 2.0.1 for TYPO3. It fails to verify whether a specified content element identifier is permitted by the plugin. This enables an unauthenticated user to display various content elements, leading to an insecure direct object reference (IDOR) issue with the potential to expose internal content elements.
CVE-2023-50461 Sep 14, 2026
TYPO3 Direct Mail <=9.5.1 Config Injection & RCE via Config Backend An issue was discovered in the direct_mail (aka Direct Mail) extension through 9.5.1 for TYPO3. The Configuration backend module of the extension allows an authenticated user to write to an arbitrary TSConfig page for folders configured as Direct Mail. Exploiting this may lead to Configuration Injection (TYPO3 10.4 and above) and to Arbitrary Code Execution (TYPO3 9.5 and below). A valid backend user account, with access to the Direct Mail Configuration backend module, is needed to exploit this.
CVE-2023-50460 Sep 14, 2026
TYPO3 femanager 7.x before 7.2.3 Authenticated Backend User Privilege Escalation An issue was discovered in the femanager extension 7.x before 7.2.3 for TYPO3. The backend module allows an authenticated backend user to perform various actions (userLogout, confirmUser, refuseUser, and resendUserConfirmation) for any frontend user in the system.
CVE-2026-77132 Sep 08, 2026
TYPO3 CMS Auth Bypass in Localization Wizard AJAX Routes (v10-14) 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.
TYPO3
CVE-2026-85400 Sep 08, 2026
TYPO3 CMS 14.2-14.3: Admin Priv escalation via config cmds 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.
TYPO3
CVE-2026-56092 Aug 25, 2026
TYPO3 CMS Extension Bypasses Subpage Access via Cached Rootline 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.
TYPO3
CVE-2026-56093 Aug 25, 2026
TYPO3 solr Extension Frontend Detail-View Bypass: SiteHash & FE Filters Not Applied 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.
TYPO3
CVE-2026-56094 Aug 25, 2026
TYPO3 Solr Ext: Unchecked Filter Injection Enables Site Hash Bypass 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.
TYPO3
CVE-2026-56095 Aug 25, 2026
TYPO3 PHP Object Injection via Unserialize in Indexer 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.
TYPO3
CVE-2026-56096 Aug 25, 2026
TYPO3 Extension: Unrestricted Solr Query Injection Enables Blind Data Extraction 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.
TYPO3
CVE-2026-77127 Aug 25, 2026
TYPO3 Extension Backend AJAX Field Disclosure The extension fails to restrict a backend AJAX endpoint for inline editing to fields the current user is permitted to see or edit. An authenticated, low-privileged backend user can supply arbitrary table, field and record parameters, and trigger an error response that discloses the current database value of the requested field, leading to disclosure of sensitive information such as backend and frontend user password hashes. Exploitation requires a valid, authenticated TYPO3 backend user account with access to the extensions backend module.
CVE-2026-77128 Aug 25, 2026
TYPO3 CMS: Unauthenticated Remote Access via Missing Enable-Field Enforcement The extension fails to enforce enable-field restrictions on a repository query parameter. An unauthenticated remote user can pass a demand-override parameter to view hidden or time-restricted events, unless the disableOverrideDemand plugin setting is active. Exploitation of this issue requires only that disableOverrideDemand is not enabled.
CVE-2026-77129 Aug 25, 2026
TYPO3 CMS Event Reg Ext. XSS via unchecked Fluid subject The extension passes an editor-configurable email subject string directly into a Fluid template source without restriction. A backend user with edit access to the event plugin or Backend Module can supply Fluid ViewHelper syntax in this field to disclose sensitive data or execute TypoScript content objects. Exploitation of this issue requires an authenticated backend account with edit access to the event registration plugin or backend module.
CVE-2026-77131 Aug 25, 2026
TYPO3 CMS Extension Sends System Info in Cleartext Without OpenSSL 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.
TYPO3
CVE-2026-77130 Aug 25, 2026
TYPO3 SysSy JWT Expiration Validation Bypass 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.
TYPO3
Built by Foundeo Inc., with data from the National Vulnerability Database (NVD). Privacy Policy. Use of this site is governed by the Legal Terms
Disclaimer
CONTENT ON THIS WEBSITE IS PROVIDED ON AN "AS IS" BASIS AND DOES NOT IMPLY ANY KIND OF GUARANTEE OR WARRANTY, INCLUDING THE WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR USE. YOUR USE OF THE INFORMATION ON THE DOCUMENT OR MATERIALS LINKED FROM THE DOCUMENT IS AT YOUR OWN RISK. Always check with your vendor for the most up to date, and accurate information.