{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-2195 exists.","fix":"No fix has been published for CVE-2025-2195 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-2195 is a medium-severity cross-site scripting vulnerability in MRCMS, published on 11 Mar 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-2195 and fix it if it is affected.\n\nWhat it is: CVE-2025-2195 is a medium-severity cross-site scripting vulnerability in MRCMS, published on 11 Mar 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-2195 exists.\n\nAffected product: MRCMS. 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-2195/ (Markdown: https://insights.sbomify.com/CVE-2025-2195/index.md)","id":"CVE-2025-2195","markdown":"https://insights.sbomify.com/CVE-2025-2195/index.md","name":"CVE-2025-2195","record":{"aliases":["GHSA-2qxm-j67j-mv87"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["code_execution","account_takeover"],"network_reachable":"yes","non_default_config":false,"product_category":"MRCMS","requires_auth":"low_privilege","summary":"Remote attackers can execute arbitrary scripts via the file rename function in MRCMS, potentially leading to session hijacking or code execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"mrcms","vendor":"mrcms"}],"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:L/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"},{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"A vulnerability was found in MRCMS 3.1.2. It has been classified as problematic. Affected is the function rename of the file /admin/file/rename.do of the component org.marker.mushroom.controller.FileController. The manipulation of the argument name/path leads to cross site scripting. It is possible to launch the attack remotely. The exploit has been disclosed to the public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"MRCMS org.marker.mushroom.controller.FileController rename.do rename cross site scripting","id":"CVE-2025-2195","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"MRCMS org.marker.mushroom.controller.FileController upload.do upload cross site scripting","id":"CVE-2025-2196"},"packages":[],"prev":{"headline":"MRCMS org.marker.mushroom.controller.FileController list.do list cross site scripting","id":"CVE-2025-2194"},"products":["MRCMS"],"published":"2025-03-11","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2026-31272","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":8.8,"headline":"SQL injection in n/a","id":"CVE-2024-48177","kev_date_added":null,"published":"2024-10-28"},{"cvss_score":7.5,"headline":"Path traversal in n/a","id":"CVE-2024-24161","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":6.5,"headline":"SQL injection in n/a","id":"CVE-2024-25428","kev_date_added":null,"published":"2024-02-20"},{"cvss_score":6.1,"headline":"Cross-site scripting in n/a","id":"CVE-2024-24160","kev_date_added":null,"published":"2024-02-02"},{"cvss_score":5.4,"headline":"Code injection in n/a","id":"CVE-2025-25768","kev_date_added":null,"published":"2025-02-21"},{"cvss_score":5.3,"headline":"Missing authorization in n/a","id":"CVE-2026-29909","kev_date_added":null,"published":"2026-03-30"}],"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":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-03-11","vendors":["n/a"]},"summary":"Remote attackers can execute arbitrary scripts via the file rename function in MRCMS, potentially leading to session hijacking or code execution.","url":"https://insights.sbomify.com/CVE-2025-2195/"}