{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-25785 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-25785 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-25785 is a critical server-side request forgery vulnerability in n/a, published on 26 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-25785 and fix it if it is affected.\n\nWhat it is: CVE-2025-25785 is a critical server-side request forgery vulnerability in n/a, published on 26 Feb 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-25785 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-25785/ (Markdown: https://insights.sbomify.com/CVE-2025-25785/index.md)","id":"CVE-2025-25785","markdown":"https://insights.sbomify.com/CVE-2025-25785/index.md","name":"CVE-2025-25785","record":{"aliases":["GHSA-xmg6-qg4m-gw97"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"JizhiCMS","requires_auth":"none","summary":"Attackers can perform intranet scans via SSRF in JizhiCMS, potentially exposing internal network resources.","user_interaction":"not_required","vuln_class":"ssrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jizhicms","vendor":"jizhicms"}],"cvss":{"score":9.1,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-918","name":"Server-Side Request Forgery"}],"description":"JizhiCMS v2.5.4 was discovered to contain a Server-Side Request Forgery (SSRF) via the component \\c\\PluginsController.php. This vulnerability allows attackers to perform an intranet scan via a crafted request.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Server-side request forgery in n/a","id":"CVE-2025-25785","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"ssrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Code injection in n/a","id":"CVE-2025-25789"},"packages":[],"prev":{"headline":"File upload in n/a","id":"CVE-2025-25784"},"products":["n/a"],"published":"2025-02-26","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-50229","kev_date_added":null,"published":"2026-04-23"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2025-25784","kev_date_added":null,"published":"2025-02-26"},{"cvss_score":9.8,"headline":"File upload in n/a","id":"CVE-2024-32161","kev_date_added":null,"published":"2024-04-17"},{"cvss_score":9.8,"headline":"Path traversal in n/a","id":"CVE-2023-51154","kev_date_added":null,"published":"2024-01-04"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2021-36484","kev_date_added":null,"published":"2023-02-03"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2022-36578","kev_date_added":null,"published":"2022-08-19"},{"cvss_score":9.8,"headline":"Server-side request forgery in n/a","id":"CVE-2022-27429","kev_date_added":null,"published":"2022-04-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":"yes","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can perform intranet scans via SSRF in JizhiCMS, potentially exposing internal network resources.","url":"https://insights.sbomify.com/CVE-2025-25785/"}