Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

CVE-2022-23503

TYPO3-CORE-SA-2022-015: Arbitrary Code Execution via Form Framework

Overview

Published
14 Dec 2022
Modified
17 Jun 2026
High CVE
2 Registry packages
0 OS packages
0 Linux distributions
Yes Fix available

Description

TYPO3 is an open source PHP based web content management system. Versions prior to 8.7.49, 9.5.38, 10.4.33, 11.5.20, and 12.1.1 are vulnerable to Code Injection. Due to the lack of separating user-submitted data from the internal configuration in the Form Designer backend module, it is 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 and a valid backend user account with access to the form module are needed to exploit this vulnerability. This issue is patched in versions 8.7.49 ELTS, 9.5.38 ELTS, 10.4.33, 11.5.20, 12.1.1.

Source: OX vulnerability database

Severity

8.8 · HIGH

CVSS 3.1 base score, scored by NVD.

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Weakness: CWE-94

Affected packages · 2

Packages affected by CVE-2022-23503
EcosystemPackageVulnerableFixed in
Composer (PHP) typo3/cms >=10.0.0, <10.4.33>=11.0.0, <11.5.20>=12.0.0, <12.1.1 10.4.3311.5.2012.1.1
Composer (PHP) typo3/cms-core >=8.0.0, <8.7.49>=9.0.0, <9.5.38>=10.0.0, <10.4.33>=11.0.0, <11.5.20>=12.0.0, <12.1.1 8.7.499.5.3810.4.3311.5.2012.1.1

Open a package to see all its vulnerabilities.

Operating systems

No Linux distribution reports this ID.

References

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.