dbcve.org
Seafile ServerApplication · Seafile

CVE-2025-65516

MEDIUM · 6.1 CVSS v3.1 Published 2025-12-04
Fix available
A fix is available. Upgrade to 13.0.12 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A stored cross-site scripting (XSS) vulnerability was discovered in Seafile Community Edition prior to version 13.0.12. When Seafile is configured with the Golang file server, an attacker can upload a crafted SVG file containing malicious JavaScript and share it using a public link. Opening the link triggers script execution in the victim's browser. This issue has been fixed in Seafile Community Edition 13.0.12.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A stored cross-site scripting (XSS) vulnerability exists in Seafile Community Edition prior to version 13.0.12 when configured with the Golang file server. Attackers can upload malicious SVG files containing JavaScript code and distribute them via public links; when victims open these links, the embedded script executes in their browsers.

MitigationUpgrade to Seafile Community Edition 13.0.12 or later. Consider implementing content-type restrictions or SVG sanitization as additional defense-in-depth measures.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Seafile ServerApplication
Affected:< 13.0.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Seafile Server version
    Run 'seaf-server --version' or check the version displayed in the Seafile web interface under the 'System Admin' > 'Server' page. Compare the version number to the affected range: versions prior to 13.0.12 are vulnerable.
    Affected if The installed version is less than 13.0.12
  2. Verify Golang file server is enabled
    Check the Seafile configuration file (seafile.conf) for the 'fileserver' section. Look for 'enabled = true' under the Golang file server configuration, or check if port 8082 (default Golang fileserver port) is in use.
    Affected if The Golang file server is enabled and in use
  3. Confirm public link sharing is enabled
    Check the Seafile web interface under 'System Admin' > 'Settings' > 'Library Sharing', or inspect the seahub_settings.py file for 'ENABLE_SHARE_TO_ALL' or similar public sharing configuration flags.
    Affected if Public link sharing is permitted for users
  4. Verify SVG file upload is permitted
    Check if there are any content-type restrictions configured in the Seafile deployment. Attempt to upload a test SVG file through the web interface or API to confirm SVG files are accepted.
    Affected if SVG file uploads are allowed without sanitization

The environment is affected if Seafile Server is version 13.0.12 or earlier, the Golang file server is enabled, and public link sharing allows distributing uploaded files.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 13.0.12 or later
Fixed in 13.0.12
Interim mitigation

Upgrade to Seafile Community Edition 13.0.12 or later. Consider implementing content-type restrictions or SVG sanitization as additional defense-in-depth measures.

Recommended fix High confidence

Seafile Community Edition 13.0.12

  1. 1. Back up the Seafile Server data directory and database before proceeding with any upgrade.
  2. 2. Download Seafile Community Edition version 13.0.12 from the official Seafile download page or repository.
  3. 3. Follow the Seafile upgrade documentation for your specific deployment (manual.seafile.com has upgrade guides for various versions).
  4. 4. Ensure the upgrade completes successfully and all services restart properly.
  5. 5. Verify the fix by attempting to upload a test SVG file through a public share link to confirm the XSS vulnerability is no longer present.
  6. 6. Review server logs to confirm normal operation post-upgrade.
Caveat Review Seafile 13.0 release notes for any database schema changes or configuration updates that may require adjustments during upgrade

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Seafile Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65516 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-65516 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data