{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66913 exists.","fix":"No fix has been published for CVE-2025-66913 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-66913 is a critical code injection vulnerability in n/a, published on 8 Jan 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-66913 and fix it if it is affected.\n\nWhat it is: CVE-2025-66913 is a critical code injection vulnerability in n/a, published on 8 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-66913 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-66913/ (Markdown: https://insights.sbomify.com/CVE-2025-66913/index.md)","id":"CVE-2025-66913","markdown":"https://insights.sbomify.com/CVE-2025-66913/index.md","name":"CVE-2025-66913","record":{"aliases":["GHSA-4993-v2g9-96m4"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JimuReport reporting tool","requires_auth":"none","summary":"Attackers can execute arbitrary Java code by supplying malicious H2 JDBC URLs to the JimuReport application.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"jimureport","vendor":"jeecg"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-94","name":"Improper Control of Generation of Code"}],"description":"JimuReport thru version 2.1.3 is vulnerable to remote code execution when processing user-controlled H2 JDBC URLs. The application passes the attacker-supplied JDBC URL directly to the H2 driver, allowing the use of certain directives to execute arbitrary Java code. A different vulnerability than CVE-2025-10770.","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":"Code injection in n/a","id":"CVE-2025-66913","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"code_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Code injection in n/a","id":"CVE-2025-66916"},"packages":[],"prev":{"headline":"Missing authorization in n/a","id":"CVE-2025-66911"},"products":["n/a"],"published":"2026-01-08","related":[{"cvss_score":9.8,"headline":"Privilege escalation in n/a","id":"CVE-2024-44893","kev_date_added":null,"published":"2024-09-10"},{"cvss_score":6.3,"headline":"jeecgboot JimuReport image path traversal","id":"CVE-2023-6307","kev_date_added":null,"published":"2023-11-27"},{"cvss_score":6.3,"headline":"jeecgboot JimuReport Template injection","id":"CVE-2023-4450","kev_date_added":null,"published":"2023-08-21"},{"cvss_score":5.3,"headline":"jeecgboot JimuReport MySQL JDBC testConnection deserialization","id":"CVE-2025-10770","kev_date_added":null,"published":"2025-09-21"},{"cvss_score":5.3,"headline":"jeecgboot JimuReport DB2 JDBC testConnection deserialization","id":"CVE-2025-10771","kev_date_added":null,"published":"2025-09-21"},{"cvss_score":5.3,"headline":"jeecgboot JimuReport Data Large Screen Template testConnection deserialization","id":"CVE-2025-8963","kev_date_added":null,"published":"2025-08-14"}],"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":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-08","vendors":["n/a"]},"summary":"Attackers can execute arbitrary Java code by supplying malicious H2 JDBC URLs to the JimuReport application.","url":"https://insights.sbomify.com/CVE-2025-66913/"}