CVE-2013-6430 is a cross-site scripting vulnerability in Spring MVC in Spring Framework versions before 3.2.2. The JavaScriptUtils.javaScriptEscape method does not properly escape Unicode line-separator and paragraph-separator characters or left and right angle brackets. Applications that rely on this method to escape user-controlled content before rendering it in HTML5 JavaScript contexts may permit script injection.
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.
6 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A historical Spring MVC cross-site scripting vulnerability mentioned for background context only.
Cross-site scripting vulnerability in the Spring JavaScript escape method when its output is rendered in HTML5 documents.
Insufficient escaping in the Spring JavaScript escape method that can result in cross-site scripting in HTML5-rendering applications.
A cross-site scripting vulnerability in the Spring Framework JavaScript escaping method when application output is rendered in HTML5 documents.
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.