Skip to main content
CVE-2025-70161VulnerabilityPublished Updated

CVE-2025-70161: n/a

Source CVE Database V5

0

Not known to be exploited · 27% EPSS · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
27.0% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 9 Jan 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

AI-suggested

1. Immediately check for and apply any firmware updates or patches released by EDIMAX addressing CVE-2025-70161. 2. 3. Segment networks to isolate vulnerable routers from critical assets and sensitive data. 4. Employ network intrusion detection systems (NIDS) to monitor for suspicious command injection patterns or unusual traffic to/from the router. 5. Change default credentials and enforce strong authentication policies to limit local exploitation risk. 6. Consider replacing affected devices with models from vendors with a stronger security track record if patches are delayed. 7. Regularly audit router configurations and logs for signs of compromise. 8. Educate IT staff on the risks of command injection and the importance of input validation in network devices. 9. Implement strict firewall rules to restrict management traffic to trusted sources only.

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.

References

Community reviews

Loading reviews…