All reports
High

TYPO3 CMS vulnerable to Arbitrary Code Execution via Form Framework

Affected versions

Version ranges need review.

Affected versions
>= 10.0.0, < 10.4.33
Fixed version
10.4.33
Affected versions
>= 9.0.0, < 9.5.38
Fixed version
9.5.38
Affected versions
>=10.0.0,<10.4.33|>=11.0.0,<11.5.20|>=12.0.0,<12.1.1
Fixed version
Not reported
Affected versions
>= 8.0.0, < 8.7.49
Fixed version
8.7.49
Affected versions
>= 11.0.0, < 11.5.20
Fixed version
11.5.20
Affected versions
>= 12.0.0, < 12.1.1
Fixed version
12.1.1
Composertypo3/cms
Affected versions
>=10.0.0,<10.4.33|>=11.0.0,<11.5.20|>=12.0.0,<12.1.1
Fixed version
Not reported
Composertypo3/cms
Affected versions
>= 12.0.0, < 12.1.1
Fixed version
12.1.1
Composertypo3/cms
Affected versions
>= 10.0.0, < 10.4.33
Fixed version
10.4.33
Composertypo3/cms
Affected versions
>= 11.0.0, < 11.5.20
Fixed version
11.5.20

Exploitation

CVE-2022-23503

Probability of exploitation in the next 30 days: 0.85%

FIRST EPSS · 2026-11-21

Description

Problem

Due to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it was possible to inject code instructions to be processed and executed via TypoScript as PHP code.

The existence of individual TypoScript instructions for a particular form item (known as formDefinitionOverrides) and a valid backend user account with access to the form module are needed to exploit this vulnerability.

Solution

Update to TYPO3 versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1 that fix the problem described above.

References

Links