serialize-javascript 7.0.1 before 7.1.3 XSS via unescaped </script in function body
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 7.1.3
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: none
- Automatable: no
- Technical impact: partial
Summary
serialize-javascript, a Node.js library used to convert JavaScript values into strings, is affected. An attacker who can control a function's source text can break out of an HTML script block and inject executable markup, enabling cross-site scripting in pages that embed the serialized output.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
serialize-javascript from 7.0.1 before 7.1.3 contains a cross-site scripting vulnerability that allows attackers to break out of HTML script elements by ending serialized function source text with an unescaped </script. Attackers controlling a function's source via a spoofed toString() can combine surrounding output delimiters and later values to inject live markup such as img onerror handlers.
Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
- Record last updated
Affected versions
- yahoo serialize-javascript
From 7.0.1 · fixed in 7.1.3
- serialize-javascriptnpm
fixed in 7.1.3