Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.
Open advisories
184 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.
Online Media Asset Handling (.youtube and .vimeo files) in the TYPO3 backend is vulnerable to denial of service. Putting large files with according file extensions results in high consumption of system resources. This can lead to exceeding limits of the current PHP process which results in a dysfunctional backend component. A valid backend user account or write access on the server system (e.g. SFTP) is needed in order to exploit this vulnerability.
Recommended action: Upgrade to 9.5.2, 8.7.21 or 7.6.32 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The Install Tool exposes the current TYPO3 version number to non-authenticated users.
Recommended action: Upgrade to 9.5.2, 8.7.21 or 7.6.32 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
It has been discovered that cookies created in the Install Tool are not hardened to be submitted only via HTTP. In combination with other vulnerabilities such as cross-site scripting it can lead to hijacking an active and valid session in the Install Tool.
Recommended action: Upgrade to 9.5.2, 8.7.21 or 7.6.32 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Failing to properly encode user input, login status display is vulnerable to cross-site scripting in the website frontend. A valid user account is needed in order to exploit this vulnerability - either a backend user or a frontend user having the possibility to modify their user profile. Template patterns that are affected are - ###FEUSER[fieldName] using system extension felogin - <!--###USERNAME###-- for regular frontend rendering (pattern can be defined individually using TypoScript setting config.USERNAMEsubstToken)
Recommended action: Upgrade to 9.5.2, 8.7.21 or 7.6.32 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Failing to properly encode user input, notifications shown in modal windows in the TYPO3 backend are vulnerable to cross-site scripting. A valid backend user account is needed in order to exploit this vulnerability.
Recommended action: Upgrade to 9.5.2, 8.7.21 or 7.6.32 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Failing to properly encode user input, online media asset rendering (.youtube and .vimeo files) is vulnerable to cross-site scripting. A valid backend user account or write access on the server system (e.g. SFTP) is needed in order to exploit this vulnerability.
Recommended action: Upgrade to 9.5.2, 8.7.21 or 7.6.32 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Due to missing file extensions in $GLOBALS['TYPO3CONFVARS']['BE'][‘fileDenyPattern’], backend users are allowed to upload .phar, .shtml, .pl or .cgi files which can be executed in certain web server setups. A valid backend user account is needed in order to exploit this vulnerability. Derivatives of Debian GNU Linux are handling .phar files as PHP applications since PHP 7.1 (for unofficial packages) and PHP 7.2 (for official packages). The file extension .shtml is bound to server side includes which are not enabled per default in most common Linux based distributions. File extension .pl and .cgi require additional handlers to be configured which is also not the case in most common distributions (except for /cgi-bin/ location).
Recommended action: Upgrade to 9.5.4 or 8.7.23 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
TYPO3’s built-in record registration functionality (aka basic shopping cart) using recs URL parameters is vulnerable to denial of service. Failing to properly ensure that anonymous user sessions are valid, attackers can use this vulnerability in order to create an arbitrary amount of individual session-data records in the database.
Recommended action: Upgrade to 8.7.21 or 7.6.32 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
It has been discovered that mechanisms used for configuration of RequireJS package loading are susceptible to information disclosure. This way a potential attack can retrieve additional information about installed system and third party extensions.
Recommended action: Upgrade to 9.5.4 or 8.7.23 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
It has been discovered that the output of field validation errors in the Form Framework is vulnerable to cross-site scripting.
Recommended action: Upgrade to 10.2.1, 9.5.12 or 8.7.30 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Failing to properly encode user input, frontend forms handled by the form framework (system extension “form”) are vulnerable to cross-site scripting.
Recommended action: Upgrade to 9.5.4 or 8.7.23 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When using the TYPO3 backend in order to create new backend user accounts, database records containing insecure or empty credentials might be persisted. When the type of user account is changed - which might be entity type or the admin flag for backend users - the backend form is reloaded in order to reflect changed configuration possibilities. However, this leads to persisting the current state as well, which can result into some of the following: - account contains empty login credentials (username and/or password) - account is incomplete and contains weak credentials (username and/or password) Albeit the functionality provided by the TYPO3 core cannot be used either with empty usernames or empty passwords, it still can be a severe vulnerability to custom authentication service implementations. This weakness cannot be directly exploited and requires interaction on purpose by some backend user having according privileges.
Recommended action: Upgrade to 9.5.4 or 8.7.23 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
It has been discovered that t3:// URL handling and typolink functionality are vulnerable to cross-site scripting. Not only regular backend forms are affected but also frontend extensions which use the rendering with typolink.
Recommended action: Upgrade to 10.2.1, 9.5.12 or 8.7.30 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
It has been discovered that backend users having limited access to specific languages are capable of modifying and creating pages in the default language which actually should be disallowed. A valid backend user account is needed in order to exploit this vulnerability.
Recommended action: Upgrade to 8.7.23 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
It has been discovered that the output table listing in the “Files” backend module is vulnerable to cross-site scripting when a file extension contains malicious sequences. Access to the file system of the server - either directly or through synchronization - is required to exploit the vulnerability.
Recommended action: Upgrade to 10.2.1, 9.5.12 or 8.7.30 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Failing to properly encode user input, templates using built-in Fluid ViewHelpers are vulnerable to cross-site scripting.
Recommended action: Upgrade to 9.5.4 or 8.7.23 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
It has been discovered that request handling in Extbase can be vulnerable to insecure deserialization. User submitted payload has to be signed with a corresponding HMAC-SHA1 using the sensitive TYPO3 encryptionKey as secret - invalid or unsigned payload is not deserialized. However, since sensitive information could have been leaked by accident (e.g. in repositories or in commonly known and unprotected backup files), there is the possibility that attackers know the private encryptionKey and are able to calculate the required HMAC-SHA1 to allow a malicious payload to be deserialized. Requirements for successfully exploiting this vulnerability (all of the following): - rendering at least one Extbase plugin in the frontend - encryptionKey has been leaked (from LocalConfiguration.php or corresponding .env file)
Recommended action: Upgrade to 9.5.12 or 8.7.30 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Failing to properly encode information from external sources, language pack handling in the install tool is vulnerable to cross-site scripting.
Recommended action: Upgrade to 9.5.4 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
It has been discovered that the Import/Export module is susceptible to broken access control. Regular backend users have access to import functionality which usually only is available to admin users or users having User TSconfig setting options.impexp.enableImportForNonAdminUser explicitly enabled. Database content to be imported however was correctly checked against users’ permissions and not affected. However it was possible to upload files by-passing restrictions of the file abstraction layer (FAL) - however this did not affect executable files which have been correctly secured by fileDenyPattern. Currently the only known vulnerability is to directly inject .form.yaml files which could be used to trigger the vulnerability of TYPO3-CORE-SA-2018-003 (privilege escalation & SQL injection) - which requires the Form Framework (ext:form) being available on an according website. CVSSv3 scoring is based on this scenario. A valid backend user account is needed in order to exploit this…
Recommended action: Upgrade to 9.5.8 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
It has been discovered backend users not having read access to specific pages still could see them in the page tree which actually should be disallowed. A valid backend user account is needed in order to exploit this vulnerability.
Recommended action: Upgrade to 9.5.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
Backend API configuration using Page TSconfig is vulnerable to arbitrary code execution and cross-site scripting. TSconfig fields of page properties in backend forms can be used to inject malicious sequences. Field tsconfigincludes is vulnerable to directory traversal leading to same scenarios as having direct access to TSconfig settings. A valid backend user account having access to modify values for fields pages.TSconfig and pages.tsconfigincludes is needed in order to exploit this vulnerability.
Recommended action: Upgrade to 9.5.8 or 8.7.27 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
It has been discovered session data of properly authenticated and logged in frontend users is kept and transformed into an anonymous user session during the logout process. This way the next user using the same client application gains access to previous session data.
Recommended action: Upgrade to 9.5.8 or 8.7.27 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
When users change their password existing sessions for that particular user account are not revoked. A valid backend or frontend user account is required in order to make use of this vulnerability.
Recommended action: Upgrade to 9.5.6 or 8.7.25 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
The element information component used to display properties of a certain record is susceptible to information disclosure. The list of references from or to the record is not properly checked for the backend user’s permissions. A valid backend user account is needed in order to exploit this vulnerability.
Recommended action: Upgrade to 9.5.8 or 8.7.27 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.
It has been discovered that login failures have been logged on the default stream with log level "warning" including plain-text user credentials.
Recommended action: Upgrade to 9.5.6 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.