Cross-site scripting via unescaped URL serialization
Published Feb 10, 2025 · Updated Aug 16, 2026
Cross-site scripting in Yahoo serialize-javascript before 6.0.2 allows attackers to execute script in a browser via crafted URL objects. The serializer's URL branch in index.js generated new URL("...") code by inserting URL.toString() output directly instead of routing that string through the package's escaping routine, leaving unsafe characters such as active in browser-consumed output. Exposure requires an application to serialize attacker-controlled URL objects and embed the result into client-side script or HTML; the consequence is browser-side code execution in that page context.
Summary
What happened
Cross-site scripting in Yahoo serialize-javascript before 6.0.2 allows attackers to execute script in a browser via crafted URL objects. The serializer's URL branch in index.js generated new URL("...") code by inserting URL.toString() output directly instead of routing that string through the package's escaping routine, leaving unsafe characters such as active in browser-consumed output. Exposure requires an application to serialize attacker-controlled URL objects and embed the result into client-side script or HTML; the consequence is browser-side code execution in that page context.
The record
- CVE
- CVE-2024-11831
- Published
- Feb 10, 2025
- Updated
- Aug 16, 2026
- Vendor
- 389 Directory Server
- Product
- Red Hat OpenShift Service Mesh 2
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 10, 2025CVE publishedPublication date reported by the CVE source.
- Aug 16, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Affected versions are unavailable in this record. Check the vendor advisory for version and patch details.
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Snyk proof of concept for unsafe URL serializationproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo