GHSA-3vg7-jw9m-pc3f
HIGHGHSA-3vg7-jw9m-pc3f is a high-severity (CVSS 8.3) Improper Input Validation vulnerability in typo3/cms-form. O3 Security confirms whether GHSA-3vg7-jw9m-pc3f is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Broken Access Control in Form Framework
Blast Radius
typo3/cms-form🐘typo3/cms-form🐘typo3/cms-form🐘typo3/cms-form🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms+2 moreReal-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 improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.
In the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default fileDenyPattern successfully blocked files like .htaccess or malicious.php. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.
A valid backend user account with access to the form module is needed to exploit this vulnerability.
Solution
Update to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.
Credits
Thanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-form | ≥ 8.0.0&&< 8.7.40 | 8.7.40 |
| 🐘Packagist | typo3/cms-form | ≥ 9.0.0&&< 9.5.25 | 9.5.25 |
| 🐘Packagist | typo3/cms-form | ≥ 10.0.0&&< 10.4.14 | 10.4.14 |
| 🐘Packagist | typo3/cms-form | ≥ 11.0.0&&< 11.1.1 | 11.1.1 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.14 | 10.4.14 |
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.1.1 | 11.1.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-form. 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-form to 8.7.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-3vg7-jw9m-pc3f 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-3vg7-jw9m-pc3f 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-3vg7-jw9m-pc3f. 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-3vg7-jw9m-pc3f in your dependencies?
O3 detects GHSA-3vg7-jw9m-pc3f across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.