GHSA-R6MM-WMHF-849M

GHSA-R6MM-WMHF-849M is a medium-severity security vulnerability in typo3/flow (composer), affecting versions >= 2.3.0, < 2.3.16. It is fixed in 2.3.16, 3.0.10, 3.1.7, 3.2.7, 3.3.5.

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

Time-Based Information Disclosure Vulnerability in Flow

The PersistedUsernamePasswordProvider was prone to a information disclosure of account existance based on timing attacks as the hashing of passwords was only done in case an account was found. We changed the core so that the provider always does a password comparison in case credentials were submitted at all.

Impact

Affected versions

typo3/flow (>= 2.3.0, < 2.3.16) typo3/flow (>= 3.0.0, < 3.0.10) typo3/flow (>= 3.1.0, < 3.1.7) typo3/flow (>= 3.2.0, < 3.2.7) typo3/flow (>= 3.3.0, < 3.3.5)

Security releases

typo3/flow → 2.3.16 (composer) typo3/flow → 3.0.10 (composer) typo3/flow → 3.1.7 (composer) typo3/flow → 3.2.7 (composer) typo3/flow → 3.3.5 (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 2.3.16 or later; typo3/flow to 3.0.10 or later; typo3/flow to 3.1.7 or later; typo3/flow to 3.2.7 or later; typo3/flow to 3.3.5 or later

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

Frequently Asked Questions

  1. What is GHSA-R6MM-WMHF-849M? GHSA-R6MM-WMHF-849M is a medium-severity security vulnerability in typo3/flow (composer), affecting versions >= 2.3.0, < 2.3.16. It is fixed in 2.3.16, 3.0.10, 3.1.7, 3.2.7, 3.3.5.
  2. Which versions of typo3/flow are affected by GHSA-R6MM-WMHF-849M? typo3/flow (composer) versions >= 2.3.0, < 2.3.16 is affected.
  3. Is there a fix for GHSA-R6MM-WMHF-849M? Yes. GHSA-R6MM-WMHF-849M is fixed in 2.3.16, 3.0.10, 3.1.7, 3.2.7, 3.3.5. Upgrade to this version or later.
  4. Is GHSA-R6MM-WMHF-849M exploitable, and should I be worried? Whether GHSA-R6MM-WMHF-849M 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-R6MM-WMHF-849M 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-R6MM-WMHF-849M?
    • Upgrade typo3/flow to 2.3.16 or later
    • Upgrade typo3/flow to 3.0.10 or later
    • Upgrade typo3/flow to 3.1.7 or later
    • Upgrade typo3/flow to 3.2.7 or later
    • Upgrade typo3/flow to 3.3.5 or later

Other vulnerabilities in typo3/flow

Stop the waste.
Protect your environment with Kodem.