All reports
High

Broken Access Control in Form Framework

Affected versions

Version ranges need review.

Affected versions
>= 9.0.0, < 9.5.25
Fixed version
9.5.25
Affected versions
>= 11.0.0, < 11.1.1
Fixed version
11.1.1
Affected versions
>= 10.0.0, < 10.4.14
Fixed version
10.4.14
Affected versions
>=10.0.0,<10.4.14|>=11.0.0,<11.1.1|>=9.0.0,<9.5.25
Fixed version
Not reported
Affected versions
>= 10.0.0, <= 10.4.13
Fixed version
10.4.14
Affected versions
>= 9.0.0, <= 9.5.24
Fixed version
9.5.25
Affected versions
>= 11.0.0, <= 11.1.0
Fixed version
11.1.1
Affected versions
>= 8.0.0, <= 8.7.39
Fixed version
8.7.40
Composertypo3/cms
Affected versions
>=10.0.0,<10.4.14|>=11.0.0,<11.1.1|>=9.0.0,<9.5.25
Fixed version
Not reported
Composertypo3/cms
Affected versions
>= 9.0.0, < 9.5.25
Fixed version
9.5.25
Composertypo3/cms
Affected versions
>= 11.0.0, < 11.1.1
Fixed version
11.1.1
Composertypo3/cms
Affected versions
>= 10.0.0, < 10.4.14
Fixed version
10.4.14

Exploitation

CVE-2021-21357

Probability of exploitation in the next 30 days: 1.61%

FIRST EPSS · 2026-11-20

Description

Problem

Due to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.

In the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default fileDenyPattern successfully blocked files like .htaccess or malicious.php. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.

A valid backend user account with access to the form module is needed to exploit this vulnerability.

Solution

Update to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.

Credits

Thanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.

References

Links

Credits

  • sushiwushi
  • waldhacker1