dbcve.org
InjectionWeakness · CWE-74

CVE-2026-9402

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-24
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable 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 found in Edimax BR-6675nD 1.12. The affected element is the function formWlanMP of the file /goform/formWlanMP of the component POST Request Handler. The manipulation of the argument ateFunc/ateGain/ateRate/ateChan/ateTxCount/e2pTx2Power1/e2pTx2Power2/e2pTx2Power3/e2pTx2Power4/e2pTx2Power5/e2pTx2Power6/e2pTx2Power7/e2pTxPower1/e2pTxPower2/e2pTxPower3/e2pTxPower4/e2pTxPower5/e2pTxPower6/e2pTxPower7/ateTxFreqOffset/ateMode/ateMacID/ateBW/ateAntenna/e2pTxFreqOffset/e2pTxPwDeltaB/e2pTxPwDeltaG/e2pTxPwDeltaMix/readE2P/e2pTxPwDeltaN results in command injection. The attack can be launched remotely. The exploit has been made public and could be used. The vendor was contacted early about this disclosure but did not respond in any way.

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-6675nD router firmware version 1.12. The formWlanMP POST request handler fails to sanitize multiple parameters (ateFunc, ateGain, ateRate, ateChan, ateTxCount, various e2pTx* and ate* parameters) before passing them to system command execution, allowing remote authenticated attackers to execute arbitrary OS commands.

MitigationSince the vendor is unresponsive and this is end-of-life hardware, mitigate by restricting network access to the router's web interface (ACLs, VPN, or disabling remote management), or replace with actively supported equipment.

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

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

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

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 the device model
    Access the router's web admin interface or check the device label/marketing materials to confirm the model is Edimax BR-6675N (BR-6675nD).
    Affected if The device is an Edimax BR-6675nD model.
  2. Check the firmware version
    Log into the router's web interface and navigate to the System Status or Firmware Upgrade page to view the installed firmware version. Compare it to version 1.12.
    Affected if The firmware version is exactly 1.12.
  3. Verify the web management interface is accessible
    Attempt to access the router's HTTP/HTTPS web interface from the LAN or WAN. The vulnerability exists in the formWlanMP POST handler.
    Affected if The web interface responds to requests and accepts POST submissions to the formWlanMP endpoint.
  4. Confirm WLAN management features are enabled
    Check the router's wireless settings or WLAN configuration pages. The vulnerable parameters (ateFunc, ateGain, ateRate, ateChan, ateTxCount, e2pTx*) relate to WLAN testing/management functions.
    Affected if WLAN management or advanced wireless testing features are accessible or enabled on the device.

A user is affected if they own an Edimax BR-6675nD router running firmware version 1.12 with the web management interface accessible and WLAN management features enabled, as the formWlanMP POST handler accepts the listed parameters without sanitization.

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 vendor is unresponsive and this is end-of-life hardware, mitigate by restricting network access to the router's web interface (ACLs, VPN, or disabling remote management), or replace with actively supported equipment.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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