{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-65516 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-65516 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-65516 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-65516 and fix it if it is affected.\n\nWhat it is: CVE-2025-65516 is a medium-severity cross-site scripting vulnerability in n/a, published on 4 Dec 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-65516 in the wild and no public exploit code.\n\nAffected product: n/a. 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-65516/ (Markdown: https://insights.sbomify.com/CVE-2025-65516/index.md)","id":"CVE-2025-65516","markdown":"https://insights.sbomify.com/CVE-2025-65516/index.md","name":"CVE-2025-65516","record":{"aliases":["GHSA-86jv-vvjm-w37g"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"Seafile Community Edition","requires_auth":"none","summary":"Attackers can execute arbitrary JavaScript in victims' browsers via crafted SVG files when the Golang file server is enabled.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"seafile_server","vendor":"seafile"}],"cvss":{"score":6.1,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"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.","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":"Cross-site scripting in n/a","id":"CVE-2025-65516","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Denial of service in n/a","id":"CVE-2025-65518"},"packages":[],"prev":{"headline":"Fetch MCP Server has a Server-Side Request Forgery (SSRF) vulnerability","id":"CVE-2025-65513"},"products":["n/a"],"published":"2025-12-04","related":[{"cvss_score":7.8,"headline":"Privilege escalation in n/a","id":"CVE-2014-5443","kev_date_added":null,"published":"2018-03-19"},{"cvss_score":7.4,"headline":"Permissions check bypass in Seafile","id":"CVE-2021-43820","kev_date_added":null,"published":"2021-12-14"},{"cvss_score":5.4,"headline":"Seafile Server has multiple stored XSS vulnerabilities","id":"CVE-2026-30587","kev_date_added":null,"published":"2026-03-25"}],"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-05","vendors":["n/a"]},"summary":"Attackers can execute arbitrary JavaScript in victims' browsers via crafted SVG files when the Golang file server is enabled.","url":"https://insights.sbomify.com/CVE-2025-65516/"}