{"answers":{"affected":"It affects 2 products.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60684 exists.","fix":"No fix has been published for CVE-2025-60684 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-60684 is a medium-severity memory corruption 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-60684 and fix it if it is affected.\n\nWhat it is: CVE-2025-60684 is a medium-severity memory corruption 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-60684 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-60684/ (Markdown: https://insights.sbomify.com/CVE-2025-60684/index.md)","id":"CVE-2025-60684","markdown":"https://insights.sbomify.com/CVE-2025-60684/index.md","name":"CVE-2025-60684","record":{"aliases":["GHSA-wjgf-7c7g-5vwr"],"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 achieve arbitrary code execution via stack buffer overflow in ToToLink router web interface.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"lr1200gb_firmware","vendor":"totolink"},{"product":"nr1800x_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:N/A:L","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"A stack buffer overflow vulnerability exists in the ToToLink LR1200GB (V9.1.0u.6619_B20230130) and NR1800X (V9.1.0u.6681_B20230703) Router firmware within the cstecgi.cgi binary (sub_42F32C function). The web interface reads the \"lang\" parameter and constructs Help URL strings using sprintf() into fixed-size stack buffers without proper length validation. Maliciously crafted input can overflow these buffers, potentially leading to arbitrary code execution or memory corruption, without requiring 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":"Memory corruption in n/a","id":"CVE-2025-60684","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-60685"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2025-60683"},"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":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-07-05","vendors":["n/a"]},"summary":"Unauthenticated attackers can achieve arbitrary code execution via stack buffer overflow in ToToLink router web interface.","url":"https://insights.sbomify.com/CVE-2025-60684/"}