NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
HIGH severity

TYPO3 CMS vulnerable to Arbitrary Code Execution via Form FrameworkGHSA-c5wx-6c2c-f7rm

HIGHFix: TYPO3/typo3@1302e88

GHSA-c5wx-6c2c-f7rm is a high-severity (CVSS 7.5) Code Injection vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.

Also known asBIT-typo3-2022-23503CVE-2022-23503
Published
Updated
Affected
8 pkgs
Patched
8 / 8
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • A successful exploit gives an attacker total control of the affected component, not partial access.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-c5wx-6c2c-f7rm.

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs58th percentile — riskier than 58% of all scored CVEsHighest risk
0.00%0.45%0.89%1.34%0.5%0.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

8 pkgs affected
🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms🐘typo3/cms🐘typo3/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

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

Affected Packages

8 total 8 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagisttypo3/cms-core≥ 8.0.0&&< 8.7.498.7.49composer require typo3/cms-core:^8.7.49
🐘Packagisttypo3/cms-core≥ 9.0.0&&< 9.5.389.5.38composer require typo3/cms-core:^9.5.38
🐘Packagisttypo3/cms-core≥ 10.0.0&&< 10.4.3310.4.33composer require typo3/cms-core:^10.4.33
🐘Packagisttypo3/cms-core≥ 11.0.0&&< 11.5.2011.5.20composer require typo3/cms-core:^11.5.20
🐘Packagisttypo3/cms-core≥ 12.0.0&&< 12.1.112.1.1composer require typo3/cms-core:^12.1.1
🐘Packagisttypo3/cms≥ 10.0.0&&< 10.4.3310.4.33composer require typo3/cms:^10.4.33

Affected Products

1 product · 5 configurations
Application
typo3typo3
≥ 12.0.0 && < 12.1.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update typo3/cms-core to 8.7.49 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c5wx-6c2c-f7rm is resolved across your whole dependency graph.

  3. Workarounds

    Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Frequently Asked Questions

### 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`](https://docs.typo3.org/c/typo3/cms-form/main/en-us/I/Concepts/FrontendRendering/Index.html#form-element-properties)) and a valid backend user account with access to the form module are needed to exploit this vulnerability. ### Solution Update to TYP
O3 Security · Impact-Aware SCA

Is GHSA-c5wx-6c2c-f7rm in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
TYPO3 CMS vulnerable to Arbitrary Code Execution via…