{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60699 exists.","fix":"No fix has been published for CVE-2025-60699 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-60699 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-60699 and fix it if it is affected.\n\nWhat it is: CVE-2025-60699 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-60699 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-60699/ (Markdown: https://insights.sbomify.com/CVE-2025-60699/index.md)","id":"CVE-2025-60699","markdown":"https://insights.sbomify.com/CVE-2025-60699/index.md","name":"CVE-2025-60699","record":{"aliases":["GHSA-g776-ww5q-qfqq"],"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 remote attackers can achieve arbitrary code execution on TOTOLINK A950RG routers via a stack buffer overflow in the web interface.","user_interaction":"not_required","vuln_class":"memory_corruption"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"a950rg_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:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-121","name":"Stack-based Buffer Overflow"}],"description":"A buffer overflow vulnerability exists in the TOTOLINK A950RG Router firmware V5.9c.4592_B20191022_ALL within the `global.so` binary. The `getSaveConfig` function retrieves the `http_host` parameter from user input via `websGetVar` and copies it into a fixed-size stack buffer (`v13`) using `strcpy()` without performing any length checks. An unauthenticated remote attacker can exploit this vulnerability by sending a specially crafted HTTP request to the router's web interface, potentially leading to arbitrary code execution.","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-60699","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"memory_corruption","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Command injection in n/a","id":"CVE-2025-60700"},"packages":[],"prev":{"headline":"Command injection in n/a","id":"CVE-2025-60698"},"products":["n/a"],"published":"2025-11-13","related":[{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-67186","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-67187","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":9.8,"headline":"Memory corruption in n/a","id":"CVE-2025-67188","kev_date_added":null,"published":"2026-02-03"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2025-45800","kev_date_added":null,"published":"2025-05-02"},{"cvss_score":9.8,"headline":"Command injection in n/a","id":"CVE-2022-25082","kev_date_added":null,"published":"2022-02-22"},{"cvss_score":7.8,"headline":"Hardcoded credentials in n/a","id":"CVE-2022-36612","kev_date_added":null,"published":"2022-08-28"},{"cvss_score":6.5,"headline":"Memory corruption in n/a","id":"CVE-2025-67189","kev_date_added":null,"published":"2026-02-03"}],"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":"2025-11-14","vendors":["n/a"]},"summary":"Unauthenticated remote attackers can achieve arbitrary code execution on TOTOLINK A950RG routers via a stack buffer overflow in the web interface.","url":"https://insights.sbomify.com/CVE-2025-60699/"}