GHSA-w765-jm6w-4hhj is a high-severity (CVSS 7.1) Cross-site Scripting (XSS) vulnerability in @webrecorder/wabac. O3 Security confirms whether GHSA-w765-jm6w-4hhj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Webrecorder packages are vulnerable to XSS through 404 error handling logic
Real-World Exposure
@webrecorder/wabac📦replaywebpage📦@webrecorder/archivewebpageReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.
Description
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.
Patches
The vulnerability is fixed in wabac.js v2.23.11.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @webrecorder/wabac | all versions | 2.23.11 |
| 📦npm | replaywebpage | all versions | 2.3.17 |
| 📦npm | @webrecorder/archivewebpage | all versions | 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update @webrecorder/wabac to 2.23.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-w765-jm6w-4hhj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-w765-jm6w-4hhj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-w765-jm6w-4hhj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-w765-jm6w-4hhj in your dependencies?
O3 detects GHSA-w765-jm6w-4hhj across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.