Loading vulnerability…
Spring Web Flow’s JavaScript RemotingHandler improperly renders error-response bodies as HTML even where the response content type is not text/html. If server error details reflect attacker-controlled input, that input can be interpreted by the browser and execute as script. Affected releases are Spring Web Flow 4.0.0, 3.0.0 through 3.0.1, and 2.5.0 through 2.5.1; older unsupported releases are also reported as affected.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A medium-severity cross-site scripting vulnerability in Spring Web Flow's JavaScript RemotingHandler. Improper HTML rendering of non-HTML error responses can permit attacker-reflected input in server error details to execute script in a user's browser.
A Spring Web Flow vulnerability where JavaScript RemotingHandler renders non-HTML error responses as HTML, enabling a browser scripting attack under specific conditions involving reflected attacker-controlled input.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.