MediumGHSA-ww7h-g2qf-7xv6CVE-2024-55922

TYPO3 Form Framework Module vulnerable to Cross-Site Request Forgery

Published 14 Jan 2025 · Updated 21 May 2025

Affected packages

typo3/cms-formComposer
Affected
>=10.0.0 <10.4.48
Fixed in
10.4.48
Update to the fixed version for your release line, for example:composer require typo3/cms-form:^10.4.48
typo3/cms-formComposer
Affected
>=11.0.0 <11.5.42
Fixed in
11.5.42
Update to the fixed version for your release line, for example:composer require typo3/cms-form:^11.5.42
typo3/cms-formComposer
Affected
>=12.0.0 <12.4.25
Fixed in
12.4.25
Update to the fixed version for your release line, for example:composer require typo3/cms-form:^12.4.25
typo3/cms-formComposer
Affected
>=13.0.0 <13.4.3
Fixed in
13.4.3
Update to the fixed version for your release line, for example:composer require typo3/cms-form:^13.4.3

Details

Problem

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: + security.backend.enforceReferrer feature is disabled, + BE/cookieSameSite configuration is set to lax or none

The vulnerability in the affected downstream component “Form Framework Module” allows attackers to manipulate or delete persisted form definitions.

Solution

Update to TYPO3 versions 11.5.42 ELTS, 12.4.25 LTS, 13.4.3 LTS that fix the problem described.

Credits

Thanks to TYPO3 core and security members Benjamin Franzke, Oliver Hader, Andreas Kienast, Torben Hansen, Elias Häußler who fixed the issue.

References

Is GHSA-ww7h-g2qf-7xv6 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected typo3/cms-form, and gives you the command that fixes it.

Scan a project free, no signupOr connect GitHub to scan every repo

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.