{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10771 exists.","fix":"No fix has been published for CVE-2025-10771 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-10771 is a medium-severity unsafe deserialization vulnerability in jeecgboot JimuReport, published on 21 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-10771 and fix it if it is affected.\n\nWhat it is: CVE-2025-10771 is a medium-severity unsafe deserialization vulnerability in jeecgboot JimuReport, published on 21 Sep 2025. Any signed-in user can exploit it over the network, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-10771 exists.\n\nAffected product: jeecgboot JimuReport. 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-10771/ (Markdown: https://insights.sbomify.com/CVE-2025-10771/index.md)","id":"CVE-2025-10771","markdown":"https://insights.sbomify.com/CVE-2025-10771/index.md","name":"CVE-2025-10771","record":{"aliases":["GHSA-5vxh-cm9f-9j4r"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"JimuReport reporting tool","requires_auth":"low_privilege","summary":"Remote attackers can trigger deserialization via the DB2 JDBC testConnection endpoint, potentially leading to code execution.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"VulDB","cpe":[{"product":"jimureport","vendor":"jeecg"}],"cvss":{"score":5.3,"severity":"medium","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P","version":"4.0"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"},{"id":"CWE-20","name":"Improper Input Validation"}],"description":"A vulnerability was determined in jeecgboot JimuReport up to 2.1.2. Affected is an unknown function of the file /drag/onlDragDataSource/testConnection of the component DB2 JDBC Handler. Executing manipulation of the argument clientRerouteServerListJNDIName can lead to deserialization. The attack can be executed remotely. The exploit has been publicly disclosed and may be utilized.","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":"jeecgboot JimuReport DB2 JDBC testConnection deserialization","id":"CVE-2025-10771","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":0,"n_references":5,"next":{"headline":"huggingface LeRobot ZeroMQ Socket lekiwi_remote.py missing authentication","id":"CVE-2025-10772"},"packages":[],"prev":{"headline":"jeecgboot JimuReport MySQL JDBC testConnection deserialization","id":"CVE-2025-10770"},"products":["JimuReport"],"published":"2025-09-21","related":[{"cvss_score":9.8,"headline":"Code injection in n/a","id":"CVE-2025-66913","kev_date_added":null,"published":"2026-01-08"},{"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 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":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2025-09-22","vendors":["jeecgboot"]},"summary":"Remote attackers can trigger deserialization via the DB2 JDBC testConnection endpoint, potentially leading to code execution.","url":"https://insights.sbomify.com/CVE-2025-10771/"}