GHSA-vp4f-wxgw-7x8x is a high-severity (CVSS 7.5) Cross-site Scripting (XSS) vulnerability in @dcl/single-sign-on-client. O3 Security confirms whether GHSA-vp4f-wxgw-7x8x is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Improper Neutralization of Script in Attributes in @dcl/single-sign-on-client
Real-World Exposure
How broadly this vulnerability is actually deployed: weekly install volume shows current usage, a proxy for how much of the ecosystem is exposed.
@dcl/single-sign-on-clientnpmDescription
Impact
Improper input validation in the init function allows arbitrary javascript to be executed using the javascript: prefix
SSO.init('javascript:alert("javascript successfully injected")')
Patches
This vulnerability was patched on version 0.1.0
Workarounds
This vulnerability can be prevented if user input correctly sanitized or there is no user input pass to the init function
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @dcl/single-sign-on-client | all versions | 0.1.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @dcl/single-sign-on-client. 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 @dcl/single-sign-on-client to 0.1.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vp4f-wxgw-7x8x 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-vp4f-wxgw-7x8x 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-vp4f-wxgw-7x8x. 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-vp4f-wxgw-7x8x in your dependencies?
O3 detects GHSA-vp4f-wxgw-7x8x across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.