{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-70161 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-70161 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-70161 is a critical command injection vulnerability in n/a, published on 9 Jan 2026. 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-70161 and fix it if it is affected.\n\nWhat it is: CVE-2025-70161 is a critical command injection vulnerability in n/a, published on 9 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: There is no known exploitation of CVE-2025-70161 in the wild and no public exploit code.\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-70161/ (Markdown: https://insights.sbomify.com/CVE-2025-70161/index.md)","id":"CVE-2025-70161","markdown":"https://insights.sbomify.com/CVE-2025-70161/index.md","name":"CVE-2025-70161","record":{"aliases":["GHSA-44vp-c93r-6656"],"analysis":{"component_type":"network_device","fix_type":"no_fix_stated","impacts":["code_execution"],"network_reachable":"yes","non_default_config":false,"product_category":"EDIMAX router","requires_auth":"none","summary":"Attackers can execute arbitrary code on EDIMAX routers by injecting commands into the pppUserName field due to unsanitized input passed to system().","user_interaction":"not_required","vuln_class":"command_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"br-6208ac_firmware","vendor":"edimax"}],"cvss":{"score":9.8,"severity":"critical","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-77","name":"Improper Neutralization of Special Elements used in a Command"}],"description":"EDIMAX BR-6208AC V2_1.02 is vulnerable to Command Injection. This arises because the pppUserName field is directly passed to a shell command via the system() function without proper sanitization. An attacker can exploit this by injecting malicious commands into the pppUserName field, allowing arbitrary code execution.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Command injection in n/a","id":"CVE-2025-70161","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"command_injection","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"Memory corruption in n/a","id":"CVE-2025-70218"},"packages":[],"prev":{"headline":"SQL injection in n/a","id":"CVE-2025-70152"},"products":["n/a"],"published":"2026-01-09","related":[{"cvss_score":6.9,"headline":"Edimax BR-6208AC auth_check_userpass2 default credentials","id":"CVE-2026-1972","kev_date_added":null,"published":"2026-02-06"},{"cvss_score":6.9,"headline":"Edimax BR-6208AC Web-based Configuration formStaDrvSetup command injection","id":"CVE-2025-15256","kev_date_added":null,"published":"2025-12-30"},{"cvss_score":6.9,"headline":"Edimax BR-6208AC Web-based Configuration formRoute command injection","id":"CVE-2025-15257","kev_date_added":null,"published":"2025-12-30"},{"cvss_score":5.3,"headline":"Edimax BR-6208AC FTP Daemon Service handle_retr path traversal","id":"CVE-2025-14910","kev_date_added":null,"published":"2025-12-19"},{"cvss_score":5.1,"headline":"Edimax BR-6208AC Web-based Configuration formALGSetup redirect","id":"CVE-2025-15258","kev_date_added":null,"published":"2025-12-30"}],"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":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-01-12","vendors":["n/a"]},"summary":"Attackers can execute arbitrary code on EDIMAX routers by injecting commands into the pppUserName field due to unsanitized input passed to system().","url":"https://insights.sbomify.com/CVE-2025-70161/"}