VulnerabilityPublished 5 Dec 2025Updated 24 Feb 2026

CVE-2025-14093: Edimax BR-6478AC V3 · OS Command Injection

Affects Edimax BR-6478AC V3Source CVE Database V5

Public exploit available · 19% EPSS · CVSS 5.1 Medium.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 4.0 base score

5.1Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 19.5% chance of exploitation in 30 days – higher than 97% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: High
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: High: The attacker requires privileges that provide significant (e.g., administrative) control over the vulnerable system allowing full access to the vulnerable system’s settings and files.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 5 Dec 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
Edimax BR-6478AC V3	Affected =1.0.15	Fixed in–

AI-suggested

Until an official patch is released, organizations should implement the following specific mitigations: 1) Disable remote management interfaces on the Edimax BR-6478AC V3 routers to prevent external exploitation. 2) Restrict network access to the router's management interface using firewall rules or network segmentation, allowing only trusted internal IP addresses. 3) Monitor network traffic and router logs for unusual command execution patterns or unexpected outbound connections indicative of compromise. 4) Replace or upgrade affected devices to models with vendor-supported firmware and active security updates where feasible. 5) Employ network intrusion detection systems (NIDS) with signatures targeting known exploit patterns for this vulnerability. 6) Educate network administrators about the vulnerability and ensure rapid incident response capabilities. 7) If possible, disable or limit the traceroute diagnostic functionality exposed at /boafrm/formTracerouteDiagnosticRun to reduce attack surface. 8) Maintain up-to-date asset inventories to identify all impacted devices for prioritized mitigation. These measures go beyond generic advice by focusing on access control, monitoring, and device replacement strategies tailored to this specific vulnerability and device.

Description

A vulnerability was detected in Edimax BR-6478AC V3 1.0.15. Impacted is the function sub_416990 of the file /boafrm/formTracerouteDiagnosticRun. The manipulation of the argument host results in os command injection. The attack can be launched remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Impact

The vulnerability enables remote attackers to execute arbitrary OS commands on affected Edimax BR-6478AC V3 routers, potentially leading to full device compromise. This can result in unauthorized control over network traffic, interception or manipulation of data, and use of the device as a pivot point for further attacks within internal networks. Although the CVSS score is medium, the absence of authentication and user interaction requirements increases exploitation likelihood. Organizations relying on these routers for perimeter security or network segmentation may face increased risk of network breaches, data exfiltration, or service disruption. The public availability of exploit code further elevates the threat, especially in environments where patching or device replacement is delayed. The impact extends to both confidentiality and integrity of network communications, with availability impact considered low but possible if attackers disrupt device functionality. The vendor's lack of response and absence of patches exacerbate the risk, leaving affected devices exposed to persistent threats.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 24 Feb 2026, 22:49 UTC

Technical details

References

Community reviews

Related threats