VulnerabilityPublished 30 Dec 2025Updated 24 Feb 2026

CVE-2025-15258: Edimax BR-6208AC · Open Redirect

Affects Edimax BR-6208ACSource CVE Database V5

Public exploit available · CVSS 5.1 Medium · end of life, no fix coming : replace or isolate Edimax BR-6208AC; no fix will be released.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 4.0 base score

5.1Medium

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

EPSS: 0.2% chance of exploitation in 30 days – higher than 18% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: None coming – the product is end of life

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: Passive
Vulnerable system confidentiality: None
Vulnerable system integrity: Low
Vulnerable system availability: None
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: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: Passive: Successful exploitation of this vulnerability requires limited interaction by the targeted user with the vulnerable system and the attacker’s payload. These interactions would be considered involuntary and do not require that the user actively subvert protections built into the vulnerable system.
Vulnerable system confidentiality: None: There is no loss of confidentiality within 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: None: There is no impact to availability within 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 30 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

No fix will be released: Edimax BR-6208AC is end of life. Replace it, or isolate it from untrusted networks until you can.

Affected software

Product	Affected	Fixed in
Edimax BR-6208AC	Affected =1.02 =1.03	Fixed in–

AI-suggested

Given the end-of-life status of the Edimax BR-6208AC V2 and absence of vendor patches, the most effective mitigation is to replace affected devices with newer, supported models that receive regular security updates. Until replacement is feasible, organizations should implement network-level controls such as web filtering or proxy solutions to block access to known malicious URLs and monitor for suspicious redirect activity. Administrators should educate users about the risks of clicking unexpected links, especially those purporting to originate from router interfaces. Network segmentation can limit exposure by isolating legacy devices from critical systems and sensitive data. Additionally, disabling remote management features or restricting access to the router’s web interface to trusted internal networks can reduce the attack surface. Logging and monitoring of router access logs may help detect exploitation attempts. Finally, organizations should maintain an inventory of network devices to identify and prioritize replacement of unsupported hardware.

Description

A weakness has been identified in Edimax BR-6208AC 1.02/1.03. Affected by this issue is the function formALGSetup of the file /goform/formALGSetup of the component Web-based Configuration Interface. This manipulation of the argument wlan-url causes open redirect. The attack is possible to be carried out remotely. The exploit has been made available to the public and could be used for attacks. Edimax confirms this issue: "The product mentioned, EDIMAX BR-6208AC V2, has reached its End of Life (EOL) status. It is no longer supported or maintained by Edimax, and it is no longer available for purchase in the market. Consequently, there will be no further firmware updates or patches for this device. We recommend users upgrade to newer models for better security." This vulnerability only affects products that are no longer supported by the maintainer.

Impact

The primary impact of this vulnerability is the potential for attackers to conduct phishing or social engineering attacks by redirecting users from the trusted router interface to malicious websites. This can lead to credential compromise, malware infection, or further exploitation of user systems. While the vulnerability does not directly compromise the router’s confidentiality, integrity, or availability, it undermines user trust and can serve as a stepping stone for more severe attacks. Organizations relying on the Edimax BR-6208AC V2 routers may face increased risk of targeted phishing campaigns against their users or administrators. Since the device is no longer supported, the inability to patch the vulnerability prolongs exposure and complicates remediation efforts. This can be particularly impactful in environments where these routers provide critical network access or are used in sensitive operational contexts. The medium severity rating reflects the moderate risk posed by the vulnerability, balancing ease of exploitation with limited direct device compromise. However, the broader security posture of affected organizations can be degraded if attackers successfully leverage the open redirect for downstream attacks.

Summary

CVE-2025-15258 identifies an open redirect vulnerability in the Edimax BR-6208AC V2 router, specifically in firmware versions 1.02 and 1.03. The vulnerability resides in the web-based configuration interface's formALGSetup function, where the wlan-url parameter is improperly validated, allowing attackers to redirect users to arbitrary external URLs. This type of vulnerability can be exploited remotely without authentication, but requires user interaction, such as clicking a maliciously crafted link. Open redirects can be leveraged in phishing campaigns to trick users into visiting malicious websites appearing to originate from a trusted source, potentially facilitating further attacks like credential theft or malware distribution. Edimax has confirmed that the BR-6208AC V2 model is end-of-life and no longer supported, meaning no firmware patches or updates will be released to address this issue. The CVSS 4.0 vector indicates network attack vector, low attack complexity, no privileges required, user interaction needed, and limited impact on integrity and availability, resulting in a medium severity rating with a score of 5.1. Although no active exploits have been reported in the wild, the public availability of exploit code increases the likelihood of exploitation attempts. The vulnerability affects only legacy devices, but those devices may still be deployed in some environments, especially where hardware replacement cycles are slow or budgets limited. The lack of vendor support necessitates alternative mitigation strategies such as network segmentation, web filtering, or device replacement to reduce risk.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

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

Technical details

References

Community reviews

Related threats