{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60683 exists.","fix":"No fix has been published for CVE-2025-60683 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-60683 is a medium-severity command injection vulnerability in n/a, published on 13 Nov 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-60683 and fix it if it is affected.\n\nWhat it is: CVE-2025-60683 is a medium-severity command injection vulnerability in n/a, published on 13 Nov 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-60683 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-60683/ (Markdown: https://insights.sbomify.com/CVE-2025-60683/index.md)","id":"CVE-2025-60683","markdown":"https://insights.sbomify.com/CVE-2025-60683/index.md","name":"CVE-2025-60683","record":{"aliases":["GHSA-q788-r29g-853f"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"ToToLink router firmware","requires_auth":"none","summary":"An attacker with write access to a specific system file can execute arbitrary commands on ToToLink A720R routers due to insufficient input validation in the sysconf binary.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"a720r_firmware","vendor":"totolink"}],"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-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"A command injection vulnerability exists in the ToToLink A720R Router firmware V4.1.5cu.614_B20230630 within the sysconf binary, specifically in the sub_40BFA4 function that handles network interface reinitialization from '/var/system/linux_vlan_reinit'. Input is only partially validated by checking the prefix of interface names, and is concatenated into shell commands executed via system() without escaping. An attacker with write access to this file can execute arbitrary commands on the device.","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":"Command injection in n/a","id":"CVE-2025-60683","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-60684"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2025-60682"},"products":["n/a"],"published":"2025-11-13","related":[{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2023-23064","kev_date_added":null,"published":"2023-02-17"},{"cvss_score":9.8,"headline":"Denial of service in n/a","id":"CVE-2021-45740","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2021-45742","kev_date_added":null,"published":"2022-02-04"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2021-35324","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":9.8,"headline":"Missing authorization in n/a","id":"CVE-2021-35327","kev_date_added":null,"published":"2021-08-05"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2021-27708","kev_date_added":null,"published":"2021-04-14"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2021-27710","kev_date_added":null,"published":"2021-04-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-07-05","vendors":["n/a"]},"summary":"An attacker with write access to a specific system file can execute arbitrary commands on ToToLink A720R routers due to insufficient input validation in the sysconf binary.","url":"https://insights.sbomify.com/CVE-2025-60683/"}