CVE-2023-41049 is a high-severity (CVSS 7.5) Cross-site Scripting (XSS) vulnerability in @dcl/single-sign-on-client. A fix is available for @dcl/single-sign-on-client — see the affected versions and patch details below.
Improper Neutralization of Script in Attributes in @dcl/single-sign-on-client
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- 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-2023-41049.
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.
@dcl/single-sign-on-clientnpmDescription
@dcl/single-sign-on-client is an open source npm library which deals with single sign on authentication flows. Improper input validation in the init function allows arbitrary javascript to be executed using the javascript: prefix. This vulnerability has been patched on version 0.1.0. Users are advised to upgrade. Users unable to upgrade should limit untrusted user input to the init function.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @dcl/single-sign-on-client | all versions | 0.1.0npm install @dcl/single-sign-on-client@0.1.0 |
Affected Products
single sign on clientdecentralandDetection & 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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 CVE-2023-41049 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-2023-41049 in your dependencies?
Find it across npm, including transitive dependencies.