Seafile Server has multiple stored XSS vulnerabilitiesGHSA-rqj3-x344-qvxc
MEDIUMFix: haiwen/seadoc-editor@8fa988aGHSA-rqj3-x344-qvxc is a medium-severity (CVSS 5.4) Cross-site Scripting (XSS) vulnerability in @seafile/sdoc-editor. A fix is available for @seafile/sdoc-editor — see the affected versions and patch details below.
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 GHSA-rqj3-x344-qvxc.
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.
@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.75npm install @seafile/sdoc-editor@3.0.75 |
| 📦npm | @seafile/sdoc-editor | all versions | 2.0.209npm install @seafile/sdoc-editor@2.0.209 |
Affected Products
seafile serverseafileDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @seafile/sdoc-editor, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
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
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 GHSA-rqj3-x344-qvxc in your dependencies?
Find it across npm, including transitive dependencies.