dbcve.org
SeafileApplication

CVE-2025-41080

MEDIUM · 6.1 CVSS v3.1 Published 2025-12-04
Fix available
A fix is available. Upgrade to 12.0.14 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 has been found in Seafile v12.0.10. This vulnerability allows an attacker to execute arbitrary code in the victim's browser by storing malicious payloads with POST parámetro 'p' in '/api/v2.1/repos/{repo_id}/file/'.

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 · moderate confidence

A stored Cross-Site Scripting (XSS) vulnerability exists in Seafile v12.0.10 where malicious JavaScript payloads can be injected via the POST parameter 'p' to the '/api/v2.1/repos/{repo_id}/file/' API endpoint. The injected script persists and executes when users view the affected file resource in the web interface.

MitigationImplement strict input validation and output encoding on the 'p' parameter in the file API endpoint. Additionally, configure Content-Security-Policy headers to mitigate XSS execution.

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
SeafileApplication
Affected:< 12.0.14

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. Verify Seafile server version
    Access the Seafile server admin interface or check the version file in the Seafile installation directory. Common locations include the admin panel 'About' page or running 'seaf-server --version' if CLI is available.
    Affected if Installed version is 12.0.10 or any version prior to 12.0.14 (e.g., 12.0.0 through 12.0.13)
  2. Confirm API endpoint accessibility
    Verify that the '/api/v2.1/repos/{repo_id}/file/' endpoint is accessible. This requires at least one repository to exist and the user to have valid authentication credentials to make API requests.
    Affected if The API endpoint is reachable and accepts POST requests with the 'p' parameter
  3. Check for file upload functionality with 'p' parameter
    Examine API requests to the file endpoint using a web proxy or server access logs. Look for POST requests containing the 'p' parameter which is used to specify file path in the API call.
    Affected if The 'p' parameter is accepted and processed by the endpoint without sanitization
  4. Inspect stored file resources for XSS payloads
    Review files stored in Seafile repositories, particularly in file metadata or filename fields that might contain injected JavaScript. Check the web interface's file viewer for unexpected script execution when viewing these files.
    Affected if Any file resource in the repository contains malicious JavaScript in fields that are rendered in the web interface without encoding
  5. Review server logs for XSS injection attempts
    Examine Seafile server logs for unusual patterns in API requests, particularly those targeting the file API endpoint with potentially malicious 'p' parameter values.
    Affected if Logs show suspicious payloads in 'p' parameter requests that match XSS patterns

A Seafile server is affected if it runs version 12.0.10 (or any version below 12.0.14), has the file API endpoint accessible, and contains files with injected JavaScript in fields rendered by the web interface.

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 12.0.14 or later
Fixed in 12.0.14
Interim mitigation

Implement strict input validation and output encoding on the 'p' parameter in the file API endpoint. Additionally, configure Content-Security-Policy headers to mitigate XSS execution.

Recommended fix Moderate confidence

Seafile 12.0.14 or later

  1. 1. Back up your current Seafile installation and database before proceeding with the upgrade.
  2. 2. Download Seafile server version 12.0.14 or later from the official Seafile download page (https://www.seafile.com/download/).
  3. 3. Stop the Seafile service using the appropriate command for your setup (e.g., 'systemctl stop seafile' or './seafile.sh stop').
  4. 4. Upgrade Seafile by running the upgrade script for your current major version (e.g., './upgrade_12.0_12.0.14.sh').
  5. 5. After upgrade completes, start the Seafile service (e.g., 'systemctl start seafile' or './seafile.sh start').
  6. 6. Verify the upgrade was successful by logging into the web interface and checking the version number.
  7. 7. Test the previously vulnerable API endpoint '/api/v2.1/repos/{repo_id}/file/' to confirm the XSS vulnerability is remediated.

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

Fix this in Seafile Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-41080 — 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-41080 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