{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-50255 exists.","fix":"No fix has been published for CVE-2025-50255 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-50255 is a high-severity vulnerability in n/a, published on 18 Sep 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-50255 and fix it if it is affected.\n\nWhat it is: CVE-2025-50255 is a high-severity vulnerability in n/a, published on 18 Sep 2025. It can only be exploited from the same machine or local 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-50255 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-50255/ (Markdown: https://insights.sbomify.com/CVE-2025-50255/index.md)","id":"CVE-2025-50255","markdown":"https://insights.sbomify.com/CVE-2025-50255/index.md","name":"CVE-2025-50255","record":{"aliases":["GHSA-2h44-qfm6-pcm9"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["security_bypass"],"network_reachable":"adjacent_or_local","non_default_config":false,"product_category":"SmartVista BackOffice","requires_auth":"none","summary":"Attackers can perform unauthorized actions on behalf of authenticated users in SmartVista BackOffice via crafted GET requests.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[],"cvss":{"score":7.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AC:L/AV:L/A:H/C:H/I:H/PR:N/S:U/UI:R","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Cross Site Request Forgery (CSRF) vulnerability in Smartvista BackOffice SmartVista Suite 2.2.22 via crafted GET request.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-50255","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-50258"},"packages":[],"prev":{"headline":"Server-side request forgery in n/a","id":"CVE-2025-50251"},"products":["n/a"],"published":"2025-09-18","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"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":"total"},"state":"PUBLISHED","updated":"2025-09-18","vendors":["n/a"]},"summary":"Attackers can perform unauthorized actions on behalf of authenticated users in SmartVista BackOffice via crafted GET requests.","url":"https://insights.sbomify.com/CVE-2025-50255/"}