Cross-Site-Request-Forgery in Backend URI Handling in Typo3
typo3
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| typo3/cms-core Packagist |
|
|
| typo3/cms Packagist |
|
|
typo3
| Product | Affected | Fixed in |
|---|---|---|
| typo3/cms-core Packagist |
|
|
| typo3/cms Packagist |
|
|
TYPO3 is an open source PHP based web content management system released under the GNU GPL. It has been discovered that the new TYPO3 v11 feature that allows users to create and share deep links in the backend user interface is vulnerable to cross-site-request-forgery. The impact is the same as described in TYPO3-CORE-SA-2020-006 (CVE-2020-11069). However, it is not limited to the same site context and does not require the attacker to be authenticated. In a worst case scenario, the attacker could create a new admin user account to compromise the system. To successfully carry out an attack, an attacker must trick his victim to access a compromised system. The victim must have an active session in the TYPO3 backend at that time. The following Same-Site cookie settings in $GLOBALS[TYPO3_CONF_VARS][BE][cookieSameSite] are required for an attack to be successful: SameSite=strict: malicious evil.example.org invoking TYPO3 application at good.example.org and SameSite=lax or none: malicious evil.com invoking TYPO3 application at example.org. Update your instance to TYPO3 version 11.5.0 which addresses the problem described.
From the CVE record · GitHub_M
TYPO3 v11 backend deep links are vulnerable to cross-site request forgery. An unauthenticated attacker could create an admin account if they trick a victim with an active TYPO3 backend session into accessing a compromised system. The attack also requires the described SameSite cookie settings and site context.
Check TYPO3 installations using Packagist packages typo3/cms-core or typo3/cms at versions >=11.2.0 and <11.5.0.