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.
TYPO3 CMS vulnerable to Arbitrary Code Execution via Form Framework
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
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.
How urgent is this, really
GHSA-c5wx-6c2c-f7rm plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 378,156 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms🐘typo3/cms🐘typo3/cmsReal-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
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 8.0.0&&< 8.7.49 | 8.7.49composer require typo3/cms-core:^8.7.49 |
| 🐘Packagist | typo3/cms-core | ≥ 9.0.0&&< 9.5.38 | 9.5.38composer require typo3/cms-core:^9.5.38 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.33 | 10.4.33composer require typo3/cms-core:^10.4.33 |
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.5.20 | 11.5.20composer require typo3/cms-core:^11.5.20 |
| 🐘Packagist | typo3/cms-core | ≥ 12.0.0&&< 12.1.1 | 12.1.1composer require typo3/cms-core:^12.1.1 |
| 🐘Packagist | typo3/cms | ≥ 10.0.0&&< 10.4.33 | 10.4.33composer require typo3/cms:^10.4.33 |
Detection & mitigation playbook
Open-source dependencyDetect
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.
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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-c5wx-6c2c-f7rm can be triaged on real exposure rather than presence alone.
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
Is GHSA-c5wx-6c2c-f7rm in your dependencies?
O3 Security finds GHSA-c5wx-6c2c-f7rm across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.