GHSA-rqj3-x344-qvxc is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in @seafile/sdoc-editor. O3 Security confirms whether GHSA-rqj3-x344-qvxc is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Seafile Server has multiple stored XSS vulnerabilities
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.
@seafile/sdoc-editornpmDescription
Multiple Stored XSS vulnerabilities exist in Seafile Server version 13.0.15,13.0.16-pro,12.0.14 and prior and fixed in 13.0.17, 13.0.17-pro, and 12.0.20-pro, via the Seadoc (sdoc) editor. The application fails to properly sanitize WebSocket messages regarding document structure updates. This allows authenticated remote attackers to inject malicious JavaScript payloads via the src attribute of embedded Excalidraw whiteboards or the href attribute of anchor tags.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 📦npm | @seafile/sdoc-editor | ≥ 3.0.0&&< 3.0.75 | 3.0.75 |
| 📦npm | @seafile/sdoc-editor | all versions | 2.0.209 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @seafile/sdoc-editor. 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 @seafile/sdoc-editor to 3.0.75 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-rqj3-x344-qvxc 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-rqj3-x344-qvxc 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-rqj3-x344-qvxc. 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-rqj3-x344-qvxc in your dependencies?
O3 detects GHSA-rqj3-x344-qvxc across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.