TYPO3 up to 11.5.41 Check cross-site request forgery

Summaryinfo

A vulnerability marked as problematic has been reported in TYPO3 up to 11.5.41. This affects an unknown function of the component Check Module. The manipulation leads to cross-site request forgery. This vulnerability is uniquely identified as CVE-2024-55945. The attack is possible to be carried out remotely. No exploit exists. It is suggested to upgrade the affected component.

Detailsinfo

A vulnerability, which was classified as problematic, has been found in TYPO3 up to 11.5.41. This issue affects an unknown code of the component Check Module. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. Using CWE to declare the problem leads to CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. Impacted is integrity. The summary by CVE is:

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 “DB Check Module” allows attackers to manipulate data through unauthorized actions. Users are advised to update to TYPO3 versions 11.5.42 ELTS which fixes the problem described. There are no known workarounds for this issue.

It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2024-55945 since 12/13/2024. The exploitation is known to be easy. The attack may be initiated remotely. No form of authentication is needed for a successful exploitation. It demands that the victim is doing some kind of user interaction. The technical details are unknown and an exploit is not publicly available.

Upgrading to version 11.5.42 eliminates this vulnerability.

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Productinfo

Type

• Content Management System

Name

• TYPO3

Version

• 11.5.0
• 11.5.1
• 11.5.2
• 11.5.3
• 11.5.4
• 11.5.5
• 11.5.6
• 11.5.7
• 11.5.8
• 11.5.9
• 11.5.10
• 11.5.11
• 11.5.12
• 11.5.13
• 11.5.14
• 11.5.15
• 11.5.16
• 11.5.17
• 11.5.18
• 11.5.19
• 11.5.20
• 11.5.21
• 11.5.22
• 11.5.23
• 11.5.24
• 11.5.25
• 11.5.26
• 11.5.27
• 11.5.28
• 11.5.29
• 11.5.30
• 11.5.31
• 11.5.32
• 11.5.33
• 11.5.34
• 11.5.35
• 11.5.36
• 11.5.37
• 11.5.38
• 11.5.39
• 11.5.40
• 11.5.41

License

• open-source

Website

• Product: https://typo3.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.

Discussion