GHSA-VH6J-WV25-8QXR

GHSA-VH6J-WV25-8QXR is a high-severity security vulnerability in typo3/flow (composer), affecting versions >= 3.0.0, < 3.0.12. It is fixed in 3.0.12, 3.1.10, 3.2.13, 3.3.13, 4.0.6.

Does this CVE actually affect you?

Kodem shows which CVEs are reachable and running in your applications, so you fix what's exploitable, not just what's listed.

Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.

Runtime intelligence, not another scanner.

Summary

Flow Bugfix Releases for Entity Security

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.

Impact

Affected versions

typo3/flow (>= 3.0.0, < 3.0.12) typo3/flow (>= 3.1.0, < 3.1.10) typo3/flow (>= 3.2.0, < 3.2.13) typo3/flow (>= 3.3.0, < 3.3.13) typo3/flow (>= 4.0.0, < 4.0.6)

Security releases

typo3/flow → 3.0.12 (composer) typo3/flow → 3.1.10 (composer) typo3/flow → 3.2.13 (composer) typo3/flow → 3.3.13 (composer) typo3/flow → 4.0.6 (composer)

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

Upgrade the following packages to resolve this vulnerability:

typo3/flow to 3.0.12 or later; typo3/flow to 3.1.10 or later; typo3/flow to 3.2.13 or later; typo3/flow to 3.3.13 or later; typo3/flow to 4.0.6 or later

Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.

Frequently Asked Questions

  1. What is GHSA-VH6J-WV25-8QXR? GHSA-VH6J-WV25-8QXR is a high-severity security vulnerability in typo3/flow (composer), affecting versions >= 3.0.0, < 3.0.12. It is fixed in 3.0.12, 3.1.10, 3.2.13, 3.3.13, 4.0.6.
  2. Which versions of typo3/flow are affected by GHSA-VH6J-WV25-8QXR? typo3/flow (composer) versions >= 3.0.0, < 3.0.12 is affected.
  3. Is there a fix for GHSA-VH6J-WV25-8QXR? Yes. GHSA-VH6J-WV25-8QXR is fixed in 3.0.12, 3.1.10, 3.2.13, 3.3.13, 4.0.6. Upgrade to this version or later.
  4. Is GHSA-VH6J-WV25-8QXR exploitable, and should I be worried? Whether GHSA-VH6J-WV25-8QXR 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
  5. What actually determines whether GHSA-VH6J-WV25-8QXR 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.
  6. How do I fix GHSA-VH6J-WV25-8QXR?
    • Upgrade typo3/flow to 3.0.12 or later
    • Upgrade typo3/flow to 3.1.10 or later
    • Upgrade typo3/flow to 3.2.13 or later
    • Upgrade typo3/flow to 3.3.13 or later
    • Upgrade typo3/flow to 4.0.6 or later

Other vulnerabilities in typo3/flow

Stop the waste.
Protect your environment with Kodem.