GHSA-fg9w-cffm-pmh2
MEDIUMGHSA-fg9w-cffm-pmh2 is a medium-severity (CVSS 5.9) CWE-1188 vulnerability in org.springframework.webflow:spring-webflow. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-fg9w-cffm-pmh2 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Insecure Default Initialization of Resource in Pivotal Spring Web Flow
Blast Radius
org.springframework.webflow:spring-webflowReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
An issue was discovered in Pivotal Spring Web Flow through 2.4.4. Applications that do not change the value of the MvcViewFactoryCreator useSpringBinding property which is disabled by default (i.e., set to 'false') can be vulnerable to malicious EL expressions in view states that process form submissions but do not have a sub-element to declare explicit data binding property mappings.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.springframework.webflow:spring-webflow | ≥ 2.4.0&&< 2.4.5 | 2.4.5 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework.webflow:spring-webflow. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.springframework.webflow:spring-webflow to 2.4.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fg9w-cffm-pmh2 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.
How O3 protects you
O3 pinpoints whether GHSA-fg9w-cffm-pmh2 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-fg9w-cffm-pmh2. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-fg9w-cffm-pmh2 in your dependencies?
O3 detects GHSA-fg9w-cffm-pmh2 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.