dbcve.org
Br 6208ac FirmwareOperating system · Edimax

CVE-2025-15257

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A security flaw has been discovered in Edimax BR-6208AC 1.02/1.03. Affected by this vulnerability is the function formRoute of the file /gogorm/formRoute of the component Web-based Configuration Interface. The manipulation of the argument strIp/strMask/strGateway results in command injection. The attack can be executed remotely. The exploit has been released to the public and may 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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Command injection vulnerability in Edimax BR-6208AC V2 (firmware 1.02/1.03) web-based configuration interface. The formRoute function in /gogorm/formRoute fails to sanitize user-supplied input in strIp, strMask, and strGateway arguments, allowing arbitrary command execution on the device. The vulnerability is remotely exploitable and has a CVSS 9.8 critical rating.

MitigationSince Edimax BR-6208AC is End of Life with no firmware updates available, the only mitigation is replacing affected devices with currently supported models. If continued use is mandatory, isolate the device behind a firewall and disable remote web management access.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Br 6208ac FirmwareOperating system
Affected:= 1.02= 1.03

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device model is Edimax BR-6208AC
    Access the router web interface and check the device information page, or check the device label/marketing packaging. The vulnerability specifically affects this model only.
    Affected if The device is not an Edimax BR-6208AC router.
  2. Identify the installed firmware version
    Log into the router web interface (typically at 192.168.2.1) and navigate to Status or System Settings to view the firmware version. Alternatively, check the admin panel for a firmware version display field.
    Affected if The firmware version is 1.02 or 1.03.
  3. Verify the web-based configuration interface is accessible
    Attempt to access the router administration page via HTTP/HTTPS (commonly http://192.168.2.1). The vulnerable formRoute function is part of this web interface at /gogorm/formRoute.
    Affected if The router web interface responds to requests and the /gogorm/formRoute endpoint is reachable.
  4. Check for evidence of exploitation attempts
    Review router system logs or web server access logs for requests to /gogorm/formRoute with unusual parameter values in strIp, strMask, or strGateway fields. Look for shell metacharacters or suspicious IP/mask/gateway patterns.
    Affected if Log entries show requests to /gogorm/formRoute containing command injection payloads or unexpected shell syntax.

You are affected if you own an Edimax BR-6208AC router running firmware version 1.02 or 1.03 with its web interface accessible from your network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since Edimax BR-6208AC is End of Life with no firmware updates available, the only mitigation is replacing affected devices with currently supported models. If continued use is mandatory, isolate the device behind a firewall and disable remote web management access.

Recommended fix High confidence

Replace with a currently supported router from a vendor that provides security patches (Edimax has confirmed no further firmware updates will be released for this EOL product)

  1. 1. Isolate the affected Edimax BR-6208AC device on a separate network segment (VLAN) to limit exposure to potential attackers.
  2. 2. If the device cannot be replaced immediately, disable remote management access (Web-based Configuration Interface) from untrusted networks using firewall rules.
  3. 3. Replace the End-of-Life Edimax BR-6208AC with a currently supported router from a vendor that provides regular security updates.
  4. 4. If the device must remain in service, monitor network traffic for suspicious patterns targeting the /gogorm/formRoute endpoint.
Caveat The Edimax BR-6208AC is End-of-Life with no security support; continuing use poses significant risk

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Br 6208ac Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15257 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-15257 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data