{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60687 exists.","fix":"No fix has been published for CVE-2025-60687 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-60687 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-60687 and fix it if it is affected.\n\nWhat it is: CVE-2025-60687 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-60687 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-60687/ (Markdown: https://insights.sbomify.com/CVE-2025-60687/index.md)","id":"CVE-2025-60687","markdown":"https://insights.sbomify.com/CVE-2025-60687/index.md","name":"CVE-2025-60687","record":{"aliases":["GHSA-7cq5-4hvg-2j88"],"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":"Unauthenticated attackers can execute arbitrary commands on ToToLink LR1200GB routers via the IMEI parameter in cstecgi.cgi.","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lr1200gb_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":"An unauthenticated command injection vulnerability exists in the ToToLink LR1200GB Router firmware V9.1.0u.6619_B20230130 within the cstecgi.cgi binary (sub_41EC68 function). The binary reads the \"imei\" parameter from a web request and verifies only that it is 15 characters long. The parameter is then directly inserted into a system command using sprintf() and executed with system(). Maliciously crafted IMEI input can execute arbitrary commands on the router without authentication.","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-60687","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-60688"},"packages":[],"prev":{"headline":"Memory corruption in n/a","id":"CVE-2025-60686"},"products":["n/a"],"published":"2025-11-13","related":[{"cvss_score":9.8,"headline":"Totolink LR1200GB Web Interface cstecgi.cgi loginAuth stack-based overflow","id":"CVE-2024-1783","kev_date_added":null,"published":"2024-02-23"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2023-46977","kev_date_added":null,"published":"2023-10-31"},{"cvss_score":8.8,"headline":"Totolink LR1200GB cstecgi.cgi setSmsCfg stack-based overflow","id":"CVE-2024-0571","kev_date_added":null,"published":"2024-01-16"},{"cvss_score":8.8,"headline":"Totolink LR1200GB cstecgi.cgi setOpModeCfg stack-based overflow","id":"CVE-2024-0572","kev_date_added":null,"published":"2024-01-16"},{"cvss_score":8.8,"headline":"Totolink LR1200GB cstecgi.cgi setDiagnosisCfg stack-based overflow","id":"CVE-2024-0573","kev_date_added":null,"published":"2024-01-16"},{"cvss_score":8.8,"headline":"Totolink LR1200GB cstecgi.cgi setParentalRules stack-based overflow","id":"CVE-2024-0574","kev_date_added":null,"published":"2024-01-16"},{"cvss_score":8.8,"headline":"Totolink LR1200GB cstecgi.cgi setTracerouteCfg stack-based overflow","id":"CVE-2024-0575","kev_date_added":null,"published":"2024-01-16"}],"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":"Unauthenticated attackers can execute arbitrary commands on ToToLink LR1200GB routers via the IMEI parameter in cstecgi.cgi.","url":"https://insights.sbomify.com/CVE-2025-60687/"}