{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-41080 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-41080 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-41080 is a medium-severity cross-site scripting vulnerability in Seafile, published on 4 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-41080 and fix it if it is affected.\n\nWhat it is: CVE-2025-41080 is a medium-severity cross-site scripting vulnerability in Seafile, published on 4 Dec 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-41080 in the wild and no public exploit code.\n\nAffected product: Seafile. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-41080/ (Markdown: https://insights.sbomify.com/CVE-2025-41080/index.md)","id":"CVE-2025-41080","markdown":"https://insights.sbomify.com/CVE-2025-41080/index.md","name":"CVE-2025-41080","record":{"aliases":["GHSA-qwww-q2vq-c559"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"Seafile file sync","requires_auth":"low_privilege","summary":"Attackers can execute arbitrary JavaScript in victims' browsers via stored XSS in Seafile file upload API.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"INCIBE","cpe":[{"product":"seafile","vendor":"seafile"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:P/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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 POST parámetro 'p' in '/api/v2.1/repos/{repo_id}/file/'.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Multiple vulnerabilities in Seafile","id":"CVE-2025-41080","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Reflected Cross-Site Scripting (XSS) in IsMyGym","id":"CVE-2025-41081"},"packages":[],"prev":{"headline":"Multiple vulnerabilities in Seafile","id":"CVE-2025-41079"},"products":["Seafile"],"published":"2025-12-04","related":[{"cvss_score":7.5,"headline":"Weak cryptography in n/a","id":"CVE-2013-7469","kev_date_added":null,"published":"2019-02-21"},{"cvss_score":6.1,"headline":"Open redirect in n/a","id":"CVE-2023-28874","kev_date_added":null,"published":"2023-12-09"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2023-28873","kev_date_added":null,"published":"2023-12-09"},{"cvss_score":5.4,"headline":"Cross-site scripting in n/a","id":"CVE-2021-30146","kev_date_added":null,"published":"2021-04-06"},{"cvss_score":5.1,"headline":"Multiple vulnerabilities in Seafile","id":"CVE-2025-41079","kev_date_added":null,"published":"2025-12-04"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-12-04","vendors":["Seafile"]},"summary":"Attackers can execute arbitrary JavaScript in victims' browsers via stored XSS in Seafile file upload API.","url":"https://insights.sbomify.com/CVE-2025-41080/"}