Vulnerability advisory
GHSA-c5wx-6c2c-f7rm
TYPO3 CMS vulnerable to Arbitrary Code Execution via Form Framework
Also known as BIT-typo3-2022-23503CVE-2022-23503
Severity
- CVSS 3.x
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Affected versions
| Affected | Fixed in |
|---|---|
8.0.0 to before 8.7.49 | 8.7.49Advisories → |
9.0.0 to before 9.5.38 | 9.5.38Advisories → |
10.0.0 to before 10.4.33 | 10.4.33Advisories → |
Also listed as affected (39) | |
11.0.0 to before 11.5.20 | 11.5.20Advisories → |
12.0.0 to before 12.1.1 | 12.1.1Advisories → |
typo3/cms Packagist
All typo3/cms advisories →| Affected | Fixed in |
|---|---|
10.0.0 to before 10.4.33 | 10.4.33Advisories → |
Also listed as affected (39) | |
11.0.0 to before 11.5.20 | 11.5.20Advisories → |
12.0.0 to before 12.1.1 | 12.1.1Advisories → |
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
References
- Webgithub.com/TYPO3/typo3/security/advisories/GHSA-c5wx-6c2c-f7rm ↗
- Advisorynvd.nist.gov/vuln/detail/CVE-2022-23503 ↗
- Webgithub.com/TYPO3/typo3/commit/1302e88565821f2159e08b5d818d28de17ecc830 ↗
- Webgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms-core/CVE-2022-23503.yaml ↗
- Webgithub.com/FriendsOfPHP/security-advisories/blob/master/typo3/cms/CVE-2022-23503.yaml ↗
- Packagegithub.com/TYPO3/typo3 ↗
- Webtypo3.org/security/advisory/typo3-core-sa-2022-015 ↗