# CVE-2026-30587: Seafile Server has multiple stored XSS vulnerabilities

> Authenticated attackers can inject malicious JavaScript via unsanitized WebSocket messages in the Seadoc editor, potentially leading to code execution or account takeover.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 25 Mar 2026
- **Updated:** 10 May 2026
- **Also known as:** GHSA-rqj3-x344-qvxc

## What is CVE-2026-30587?

CVE-2026-30587 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

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

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2026-30587?

4 open source packages ship an affected version, including @seafile/sdoc-editor. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@seafile/sdoc-editor` | npm | All versions | 2.0.209 |
| `@seafile/sdoc-editor` | npm | All versions | 2.0.209 |
| `@seafile/sdoc-editor` | npm | From 3.0.0 | 3.0.75 |
| `@seafile/sdoc-editor` | npm | From 3.0.0 | 3.0.75 |

Products: Seafile Seafile Server.

## How do I fix CVE-2026-30587?

Upgrade @seafile/sdoc-editor to a fixed version for your release line: 2.0.209 or 3.0.75.

## Is CVE-2026-30587 being exploited?

There is no known exploitation of CVE-2026-30587 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2014-5443](https://insights.sbomify.com/CVE-2014-5443/): Privilege escalation in n/a (high 7.8)
- [CVE-2021-43820](https://insights.sbomify.com/CVE-2021-43820/): Permissions check bypass in Seafile (high 7.4)
- [CVE-2025-65516](https://insights.sbomify.com/CVE-2025-65516/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-30587 and fix it if it is affected.

What it is: CVE-2026-30587 is a medium-severity cross-site scripting vulnerability in n/a, published on 25 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-30587 in the wild and no public exploit code.

Affected packages and fixed versions:
- @seafile/sdoc-editor (npm): affected all versions; fixed in 2.0.209
- @seafile/sdoc-editor (npm): affected all versions; fixed in 2.0.209
- @seafile/sdoc-editor (npm): affected from 3.0.0; fixed in 3.0.75
- @seafile/sdoc-editor (npm): affected from 3.0.0; fixed in 3.0.75

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-30587/ (Markdown: https://insights.sbomify.com/CVE-2026-30587/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-30587
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-30587
- OSV: https://osv.dev/vulnerability/CVE-2026-30587

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-30587/
Summaries are generated and may contain mistakes; the official description above is the record.