{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-14012 exists.","fix":"No fix has been published for CVE-2025-14012 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-14012 is a medium-severity SQL injection vulnerability in JIZHICMS, published on 4 Dec 2025. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-14012 and fix it if it is affected.\n\nWhat it is: CVE-2025-14012 is a medium-severity SQL injection vulnerability in JIZHICMS, published on 4 Dec 2025. 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-14012 exists.\n\nAffected product: JIZHICMS. 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-14012/ (Markdown: https://insights.sbomify.com/CVE-2025-14012/index.md)","id":"CVE-2025-14012","markdown":"https://insights.sbomify.com/CVE-2025-14012/index.md","name":"CVE-2025-14012","record":{"aliases":["GHSA-m282-p3vv-884c"],"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","requires_auth":"high_privilege","summary":"Remote attackers can exploit SQL injection in JIZHICMS batch comment deletion to read or modify database contents.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"jizhicms","vendor":"jizhicms"}],"cvss":{"score":5.1,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"},{"id":"CWE-74","name":"Improper Neutralization of Special Elements in Output Used by a Downstream Component"}],"description":"A vulnerability was determined in JIZHICMS up to 2.5.5. The affected element is the function deleteAll/findAll/delete of the file /index.php/admins/Comment/deleteAll.html of the component Batch Delete Comments. Executing a manipulation can lead to sql injection. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized. 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":"JIZHICMS Batch Delete Comments deleteAll.html delete sql injection","id":"CVE-2025-14012","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"sql_injection","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"JIZHICMS Comment addcomment.html cross site scripting","id":"CVE-2025-14013"},"packages":[],"prev":{"headline":"JIZHICMS Add Display Name Field addcomment.html commentlist sql injection","id":"CVE-2025-14011"},"products":["JIZHICMS"],"published":"2025-12-04","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-02-24","vendors":["n/a"]},"summary":"Remote attackers can exploit SQL injection in JIZHICMS batch comment deletion to read or modify database contents.","url":"https://insights.sbomify.com/CVE-2025-14012/"}