How severe is GHSA-2p4f-vc9q-r5vp?

No CVSS score has been assigned to GHSA-2p4f-vc9q-r5vp yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-2p4f-vc9q-r5vp?

GHSA-2p4f-vc9q-r5vp affects the following packages: typo3/flow (Packagist), typo3/flow (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-2p4f-vc9q-r5vp?

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.

How do I detect GHSA-2p4f-vc9q-r5vp in my Packagist dependencies?

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.

How do I mitigate GHSA-2p4f-vc9q-r5vp if there is no patch (or I can't update yet)?

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Is GHSA-2p4f-vc9q-r5vp actively exploited in the wild?

No public exploit code has been indexed for GHSA-2p4f-vc9q-r5vp 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.

When was GHSA-2p4f-vc9q-r5vp published, and has it been updated?

GHSA-2p4f-vc9q-r5vp was published on June 5, 2024 and was last updated on December 2, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

Typo3 Arbitrary file upload and XML External Entity…

Real-World Exposure

2 pkgs affected

🐘typo3/flow🐘typo3/flow

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

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

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/flow`	≥ 2.3.0&&< 2.3.7	2.3.7`composer require typo3/flow:^2.3.7`
🐘Packagist	`typo3/flow`	≥ 3.0.0&&< 3.0.1	3.0.1`composer require typo3/flow:^3.0.1`

Detection & mitigation playbook

Open-source dependency

Detect
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
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

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 v

O3 Security · Impact-Aware SCA

Is GHSA-2p4f-vc9q-r5vp in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Typo3 Arbitrary file upload and XML External Entity processingGHSA-2p4f-vc9q-r5vp