CVE-2025-41079
BaseFortify
Publication date: 2025-12-04
Last updated on: 2025-12-05
Assigner: Spanish National Cybersecurity Institute, S.A. (INCIBE)
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| seafile | seafile | to 12.0.14 (exc) |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
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]
How can this vulnerability impact me? :
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]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
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]
What immediate steps should I take to mitigate this vulnerability?
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]