{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60830 exists.","fix":"No fix has been published for CVE-2025-60830 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-60830 is a medium-severity unsafe deserialization vulnerability in n/a, published on 8 Oct 2025. 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-60830 and fix it if it is affected.\n\nWhat it is: CVE-2025-60830 is a medium-severity unsafe deserialization vulnerability in n/a, published on 8 Oct 2025. 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-60830 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-60830/ (Markdown: https://insights.sbomify.com/CVE-2025-60830/index.md)","id":"CVE-2025-60830","markdown":"https://insights.sbomify.com/CVE-2025-60830/index.md","name":"CVE-2025-60830","record":{"aliases":["GHSA-4cpv-cc6h-qf28"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ERP system","requires_auth":"none","summary":"Attackers can execute arbitrary code on RedDragon ERP by exploiting a deserialization vulnerability using the default Shiro key.","user_interaction":"not_required","vuln_class":"deserialization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"redragon-erp","vendor":"redragon-erp"}],"cvss":{"score":6.5,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-502","name":"Deserialization of Untrusted Data"}],"description":"redragon-erp v1.0 was discovered to contain a Shiro deserialization vulnerability caused by the default Shiro key.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":null,"headline":"Deserialization in n/a","id":"CVE-2025-60830","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"deserialization","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"XML external entity in n/a","id":"CVE-2025-60833"},"packages":[],"prev":{"headline":"Deserialization in n/a","id":"CVE-2025-60828"},"products":["n/a"],"published":"2025-10-08","related":[],"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-10-08","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code on RedDragon ERP by exploiting a deserialization vulnerability using the default Shiro key.","url":"https://insights.sbomify.com/CVE-2025-60830/"}