dbcve.org
Br 6208ac FirmwareOperating system · Edimax

CVE-2025-15256

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 vulnerability was identified in Edimax BR-6208AC 1.02/1.03. Affected is the function formStaDrvSetup of the file /goform/formStaDrvSetup of the component Web-based Configuration Interface. The manipulation of the argument rootAPmac leads to command injection. Remote exploitation of the attack is possible. The exploit is publicly available and might be used. 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 wireless router's web interface. The formStaDrvSetup function in /goform/formStaDrvSetup accepts user-supplied input for the rootAPmac parameter without proper sanitization, allowing an attacker to inject arbitrary shell commands. This is exploitable remotely with CVSS 9.8 severity.

MitigationSince the device is End-of-Life with no patches available, the only viable mitigations are: (1) replace the device with a supported model, or (2) isolate the device on a restricted network segment with firewall rules blocking external access to the web management interface.

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. Identify device model and firmware version
    Access the router's web administration interface and navigate to the System Status or Firmware Upgrade page to view the current firmware version. Alternatively, check the label on the device or any documentation.
    Affected if The device is an Edimax BR-6208AC V2 running firmware version 1.02 or 1.03.
  2. Verify the vulnerable form endpoint exists
    Attempt to access the URI /goform/formStaDrvSetup via HTTP GET request to confirm the web server responds. This can be done with: curl -s -o /dev/null -w '%{http_code}' http://<router-ip>/goform/formStaDrvSetup
    Affected if The web server responds with a 200 or 404 status code, indicating the interface is active and the device may be exploitable.
  3. Confirm web management interface accessibility
    Check if the router's web interface is reachable from the network. This can be done by attempting to access the main login page: curl -s -o /dev/null -w '%{http_code}' http://<router-ip>/
    Affected if The web management interface is accessible from the network, enabling remote exploitation of the command injection flaw.

You are affected if you own an Edimax BR-6208AC V2 router with firmware 1.02 or 1.03 and its web management interface is reachable 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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the device is End-of-Life with no patches available, the only viable mitigations are: (1) replace the device with a supported model, or (2) isolate the device on a restricted network segment with firewall rules blocking external access to the web management interface.

Fix this in Br 6208ac Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,980
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-15256 — 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-15256 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