{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70397 exists.","fix":"No fix has been published for CVE-2025-70397 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-70397 is a high-severity SQL injection vulnerability in n/a, published on 17 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-70397 and fix it if it is affected.\n\nWhat it is: CVE-2025-70397 is a high-severity SQL injection vulnerability in n/a, published on 17 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70397 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-70397/ (Markdown: https://insights.sbomify.com/CVE-2025-70397/index.md)","id":"CVE-2025-70397","markdown":"https://insights.sbomify.com/CVE-2025-70397/index.md","name":"CVE-2025-70397","record":{"aliases":["GHSA-hxj5-g9j8-xgph"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"jizhicms CMS","requires_auth":"high_privilege","summary":"Attackers can execute arbitrary SQL commands via the data parameter in deleteAll functions, potentially reading or modifying database content.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jizhicms","vendor":"jizhicms"}],"cvss":{"score":7.2,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"jizhicms 2.5.6 is vulnerable to SQL Injection in Article/deleteAll and Extmolds/deleteAll via the data parameter.","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":"SQL injection in n/a","id":"CVE-2025-70397","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"DO NOT USE THIS CVE RECORD.","id":"CVE-2025-70420"},"packages":[],"prev":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-70368"},"products":["n/a"],"published":"2026-02-17","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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Attackers can execute arbitrary SQL commands via the data parameter in deleteAll functions, potentially reading or modifying database content.","url":"https://insights.sbomify.com/CVE-2025-70397/"}