CVE-2025-41079
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-12-04

Last updated on: 2025-12-05

Assigner: Spanish National Cybersecurity Institute, S.A. (INCIBE)

Description
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 PUT parΓ‘metro 'name' in '/api/v2.1/user/'.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-12-04
Last Modified
2025-12-05
Generated
2026-06-16
AI Q&A
2025-12-04
EPSS Evaluated
2026-06-15
NVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
seafile seafile to 12.0.14 (exc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

CVE-2025-41079 is a stored Cross-Site Scripting (XSS) vulnerability in Seafile versions prior to 12.0.14. It allows an attacker to inject malicious code via the PUT parameter 'name' in the '/api/v2.1/user/' endpoint. This malicious code is stored and later executed in the victim's browser when the data is rendered, enabling the attacker to run arbitrary scripts. [1]

Impact Analysis

This vulnerability can impact you by allowing attackers to execute arbitrary code in your browser when you interact with the affected Seafile instance. This can lead to theft of sensitive information, session hijacking, or other malicious actions performed on your behalf within the application. [1]

Detection Guidance

This vulnerability can be detected by testing the PUT parameter 'name' in the '/api/v2.1/user/' endpoint for stored Cross-Site Scripting (XSS) payloads. You can use tools like curl to send crafted PUT requests with malicious scripts in the 'name' parameter and then check if the payload is stored and executed when retrieved. For example, a command to test might be: curl -X PUT -H "Content-Type: application/json" -d '{"name":"<script>alert(1)</script>"}' https://your-seafile-server/api/v2.1/user/ followed by accessing the user data to see if the script executes. [1]

Mitigation Strategies

The immediate step to mitigate this vulnerability is to upgrade Seafile to version 12.0.14 or later, where the issue has been fixed. Additionally, avoid using vulnerable versions and consider applying input validation or sanitization on the 'name' parameter if upgrading is not immediately possible. [1]

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-41079. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart