{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-70311 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-70311 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-70311 is a medium-severity SQL injection vulnerability in n/a, published on 3 Feb 2026. 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-70311 and fix it if it is affected.\n\nWhat it is: CVE-2025-70311 is a medium-severity SQL injection vulnerability in n/a, published on 3 Feb 2026. 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-70311 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-70311/ (Markdown: https://insights.sbomify.com/CVE-2025-70311/index.md)","id":"CVE-2025-70311","markdown":"https://insights.sbomify.com/CVE-2025-70311/index.md","name":"CVE-2025-70311","record":{"aliases":["GHSA-x2gm-g5r6-83jw"],"analysis":{"component_type":"web_application","fix_type":"no_fix_stated","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"JEEWMS","requires_auth":"none","summary":"Attackers can inject malicious SQL via id1 and id2 parameters in the systemControl interface of JEEWMS, potentially compromising data integrity and confidentiality.","user_interaction":"not_required","vuln_class":"sql_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jeewms","vendor":"huayi-tec"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-89","name":"Improper Neutralization of Special Elements used in an SQL Command"}],"description":"JEEWMS 1.0 is vulnerable to SQL Injection. Attackers can inject malicious SQL statements through the id1 and id2 parameters in the /systemControl.do interface for attack.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"SQL injection in n/a","id":"CVE-2025-70311","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":"Memory corruption in n/a","id":"CVE-2025-70314"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-70310"},"products":["n/a"],"published":"2026-02-03","related":[{"cvss_score":9.4,"headline":"SQL injection in n/a","id":"CVE-2025-60269","kev_date_added":null,"published":"2025-10-10"},{"cvss_score":8.1,"headline":"File upload in n/a","id":"CVE-2024-57761","kev_date_added":null,"published":"2025-01-14"},{"cvss_score":6.9,"headline":"Guangzhou Huayi Intelligent Technology Jeewms wmOmNoticeHController.do path traversal","id":"CVE-2025-0390","kev_date_added":null,"published":"2025-01-11"},{"cvss_score":6.9,"headline":"Guangzhou Huayi Intelligent Technology Jeewms Druid Monitoring Interface index.html improper authorization","id":"CVE-2024-12347","kev_date_added":null,"published":"2024-12-08"},{"cvss_score":6.9,"headline":"Guangzhou Huayi Intelligent Technology Jeewms WmOmNoticeHController.java preHandle information disclosure","id":"CVE-2024-11961","kev_date_added":null,"published":"2024-11-28"},{"cvss_score":6.5,"headline":"File upload in n/a","id":"CVE-2025-60268","kev_date_added":null,"published":"2025-10-10"}],"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":"partial"},"state":"PUBLISHED","updated":"2026-02-11","vendors":["n/a"]},"summary":"Attackers can inject malicious SQL via id1 and id2 parameters in the systemControl interface of JEEWMS, potentially compromising data integrity and confidentiality.","url":"https://insights.sbomify.com/CVE-2025-70311/"}