Summary
Typo3 Arbitrary file upload and XML External Entity processing
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.
Impact
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
typo3/flow to 2.3.7 or later; typo3/flow to 3.0.1 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is GHSA-2P4F-VC9Q-R5VP? GHSA-2P4F-VC9Q-R5VP is a medium-severity security vulnerability in typo3/flow (composer), affecting versions >= 2.3.0, < 2.3.7. It is fixed in 2.3.7, 3.0.1.
- Which versions of typo3/flow are affected by GHSA-2P4F-VC9Q-R5VP? typo3/flow (composer) versions >= 2.3.0, < 2.3.7 is affected.
- Is there a fix for GHSA-2P4F-VC9Q-R5VP? Yes. GHSA-2P4F-VC9Q-R5VP is fixed in 2.3.7, 3.0.1. Upgrade to this version or later.
- Is GHSA-2P4F-VC9Q-R5VP exploitable, and should I be worried? Whether GHSA-2P4F-VC9Q-R5VP is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether GHSA-2P4F-VC9Q-R5VP is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix GHSA-2P4F-VC9Q-R5VP?
- Upgrade
typo3/flowto 2.3.7 or later - Upgrade
typo3/flowto 3.0.1 or later
- Upgrade