{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25461 exists.","fix":"No fix has been published for CVE-2025-25461 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25461 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Feb 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-25461 and fix it if it is affected.\n\nWhat it is: CVE-2025-25461 is a medium-severity cross-site scripting vulnerability in n/a, published on 28 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-25461 exists.\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-25461/ (Markdown: https://insights.sbomify.com/CVE-2025-25461/index.md)","id":"CVE-2025-25461","markdown":"https://insights.sbomify.com/CVE-2025-25461/index.md","name":"CVE-2025-25461","record":{"aliases":["GHSA-hcjx-v7fg-j456"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"SeedDMS document management","requires_auth":"low_privilege","summary":"Attackers can inject malicious scripts into category names, leading to XSS execution in victims' browsers when viewing associated documents.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"seeddms","vendor":"seeddms"}],"cvss":{"score":5.4,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/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 exists in SeedDMS 6.0.29. A user or rogue admin with the \"Add Category\" permission can inject a malicious XSS payload into the category name field. When a document is subsequently associated with this category, the payload is stored on the server and rendered without proper sanitization or output encoding. This results in the XSS payload executing in the browser of any user who views the document.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":"2025-02-26","github_poc":1,"max_poc_stars":2,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-02-26T04:16:08Z","kind":"github_poc","ref":"https://github.com/RoNiXxCybSeC0101/CVE-2025-25461","stars":2,"title":"SeedDMS Stored Cross Site Scripting(XSS)"}],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site scripting in n/a","id":"CVE-2025-25461","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"SQL injection in n/a","id":"CVE-2025-25462"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-25460"},"products":["n/a"],"published":"2025-02-28","related":[{"cvss_score":9.8,"headline":"Weak cryptography in n/a","id":"CVE-2022-44938","kev_date_added":null,"published":"2022-12-08"},{"cvss_score":8.8,"headline":"Privilege escalation in n/a","id":"CVE-2021-33223","kev_date_added":null,"published":"2023-06-07"},{"cvss_score":8.8,"headline":"File upload in n/a","id":"CVE-2018-12940","kev_date_added":null,"published":"2018-07-31"},{"cvss_score":8.8,"headline":"Command injection in n/a","id":"CVE-2018-12941","kev_date_added":null,"published":"2018-07-31"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2018-12942","kev_date_added":null,"published":"2018-07-31"},{"cvss_score":7.5,"headline":"File upload in n/a","id":"CVE-2019-12744","kev_date_added":null,"published":"2019-06-20"},{"cvss_score":7.2,"headline":"Code injection in n/a","id":"CVE-2025-45752","kev_date_added":null,"published":"2025-05-21"}],"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-02-28","vendors":["n/a"]},"summary":"Attackers can inject malicious scripts into category names, leading to XSS execution in victims' browsers when viewing associated documents.","url":"https://insights.sbomify.com/CVE-2025-25461/"}