How severe is GHSA-c5wx-6c2c-f7rm?

GHSA-c5wx-6c2c-f7rm has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-c5wx-6c2c-f7rm?

GHSA-c5wx-6c2c-f7rm affects the following packages: typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms (Packagist), typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-c5wx-6c2c-f7rm?

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.

How do I detect GHSA-c5wx-6c2c-f7rm in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-c5wx-6c2c-f7rm if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-c5wx-6c2c-f7rm?

O3 pinpoints whether GHSA-c5wx-6c2c-f7rm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-c5wx-6c2c-f7rm actively exploited in the wild?

No public exploit code has been indexed for GHSA-c5wx-6c2c-f7rm yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-c5wx-6c2c-f7rm?

GHSA-c5wx-6c2c-f7rm has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 51th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-c5wx-6c2c-f7rm?

GHSA-c5wx-6c2c-f7rm is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-c5wx-6c2c-f7rm published, and has it been updated?

GHSA-c5wx-6c2c-f7rm was published on December 13, 2022 and was last updated on December 6, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

GHSA-c5wx-6c2c-f7rm

HIGH

TYPO3 CMS vulnerable to Arbitrary Code Execution via Form Framework

Also known asBIT-typo3-2022-23503CVE-2022-23503

Published

Dec 13, 2022

Updated

Dec 6, 2023

Affected

8 pkgs

Patched

8 / 8

Exploits

None indexed

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk51th percentile+0.33%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

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

TYPO3-CORE-SA-2022-015

Affected Packages

8 total 8 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-core`	≥ 8.0.0&&< 8.7.49	8.7.49
🐘Packagist	`typo3/cms-core`	≥ 9.0.0&&< 9.5.38	9.5.38
🐘Packagist	`typo3/cms-core`	≥ 10.0.0&&< 10.4.33	10.4.33
🐘Packagist	`typo3/cms-core`	≥ 11.0.0&&< 11.5.20	11.5.20
🐘Packagist	`typo3/cms-core`	≥ 12.0.0&&< 12.1.1	12.1.1
🐘Packagist	`typo3/cms`	≥ 10.0.0&&< 10.4.33	10.4.33

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-c5wx-6c2c-f7rm is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-c5wx-6c2c-f7rm. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 detects GHSA-c5wx-6c2c-f7rm across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works