How severe is GHSA-vh6j-wv25-8qxr?

No CVSS score has been assigned to GHSA-vh6j-wv25-8qxr yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-vh6j-wv25-8qxr?

GHSA-vh6j-wv25-8qxr affects the following packages: typo3/flow (Packagist), typo3/flow (Packagist), typo3/flow (Packagist), typo3/flow (Packagist), typo3/flow (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-vh6j-wv25-8qxr?

Update typo3/flow to 3.0.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vh6j-wv25-8qxr is resolved across your whole dependency graph.

How do I detect GHSA-vh6j-wv25-8qxr 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-vh6j-wv25-8qxr if there is no patch (or I can't update yet)?

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.

Is GHSA-vh6j-wv25-8qxr actively exploited in the wild?

No public exploit code has been indexed for GHSA-vh6j-wv25-8qxr 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-vh6j-wv25-8qxr published, and has it been updated?

GHSA-vh6j-wv25-8qxr 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.

Flow Bugfix Releases for Entity Security

Real-World Exposure

5 pkgs affected

🐘typo3/flow🐘typo3/flow🐘typo3/flow🐘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

If you had used entity security and wanted to secure entities not just based on the user's role, but on some property of the user (like the company he belongs to), entity security did not work properly together with the doctrine query cache. This could lead to other users re-using SQL queries from the cache which were built for other users; and thus users could see entities which were not destined for them.

Affected Packages

5 total 5 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/flow`	≥ 3.0.0&&< 3.0.12	3.0.12`composer require typo3/flow:^3.0.12`
🐘Packagist	`typo3/flow`	≥ 3.1.0&&< 3.1.10	3.1.10`composer require typo3/flow:^3.1.10`
🐘Packagist	`typo3/flow`	≥ 3.2.0&&< 3.2.13	3.2.13`composer require typo3/flow:^3.2.13`
🐘Packagist	`typo3/flow`	≥ 3.3.0&&< 3.3.13	3.3.13`composer require typo3/flow:^3.3.13`
🐘Packagist	`typo3/flow`	≥ 4.0.0&&< 4.0.6	4.0.6`composer require typo3/flow:^4.0.6`

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 3.0.12 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vh6j-wv25-8qxr 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.

Frequently Asked Questions

If you had used entity security and wanted to secure entities not just based on the user's role, but on some property of the user (like the company he belongs to), entity security did not work properly together with the doctrine query cache. This could lead to other users re-using SQL queries from the cache which were built for other users; and thus users could see entities which were not destined for them.

O3 Security · Impact-Aware SCA

Is GHSA-vh6j-wv25-8qxr in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

Flow Bugfix Releases for Entity SecurityGHSA-vh6j-wv25-8qxr