GHSA-2p4f-vc9q-r5vp — typo3/flow
GHSA-2p4f-vc9q-r5vp is a security vulnerability in typo3/flow. A fix is available for typo3/flow — see the affected versions and patch details below.
Typo3 Arbitrary file upload and XML External Entity processing
Real-World Exposure
typo3/flow🐘typo3/flowReal-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
It has been discovered that Flow 3.0.0 allows arbitrary file uploads, inlcuding server-side scripts, posing the risk of attacks. If those scripts are executed by the server when accessed through their public URL, anything not blocked through other means is possible (information disclosure, placement of backdoors, data removal, …).
Note: The upload of files is only possible if the application built on Flow provides means to do so, and whether or not the upload of files poses a risk is dependent on the system setup. If uploaded script files are not executed by the server, there is no risk. In versions prior to 3.0.0 the upload of files with the extension php was blocked.
In Flow 2.3.0 to 2.3.6 a potential XML External Entity processing vulnerability has been discovered in the MediaTypeConverter.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/flow | ≥ 2.3.0&&< 2.3.7 | 2.3.7composer require typo3/flow:^2.3.7 |
| 🐘Packagist | typo3/flow | ≥ 3.0.0&&< 3.0.1 | 3.0.1composer require typo3/flow:^3.0.1 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/flow, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/flow to 2.3.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-2p4f-vc9q-r5vp 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-2p4f-vc9q-r5vp can be triaged on real exposure rather than presence alone.
Tailored to GHSA-2p4f-vc9q-r5vp. 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-2p4f-vc9q-r5vp in your dependencies?
O3 Security finds GHSA-2p4f-vc9q-r5vp across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.