CVE-2025-58765 is a high-severity (CVSS 7.1) Cross-site Scripting (XSS) vulnerability in @webrecorder/wabac. A fix is available for @webrecorder/wabac — see the affected versions and patch details below.
wabac.js has XSS vulnerability in 404 error handling logic
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-58765.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.
@webrecorder/wabacnpmreplaywebpagenpm@webrecorder/archivewebpagenpmDescription
wabac.js provides a full web archive replay system, or 'wayback machine', using Service Workers. A Reflected Cross-Site Scripting (XSS) vulnerability exists in the 404 error handling logic of wabac.js v2.23.10 and below. The parameter requestURL (derived from the original request target) is directly embedded into an inline <script> block without sanitization or escaping. This allows an attacker to craft a malicious URL that executes arbitrary JavaScript in the victim’s browser. The scope may be limited by CORS policies, depending on the situation in which wabac.js is used. The vulnerability is fixed in wabac.js v2.23.11.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @webrecorder/wabac | all versions | 2.23.11npm install @webrecorder/wabac@2.23.11 |
| 📦npm | replaywebpage | all versions | 2.3.17npm install replaywebpage@2.3.17 |
| 📦npm | @webrecorder/archivewebpage | all versions | 0.15.4npm install @webrecorder/archivewebpage@0.15.4 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @webrecorder/wabac, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @webrecorder/wabac to 2.23.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-58765 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is CVE-2025-58765 in your dependencies?
Find it across npm, including transitive dependencies.