dbcve.org
InjectionWeakness · CWE-74

CVE-2026-9378

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 security flaw has been discovered in Edimax BR-6675nD 1.12. This affects the function formHwSet of the file /goform/formHwSet of the component POST Request Handler. The manipulation of the argument regDomain/ABandregDomain/nic0Addr/nic1Addr/wlanAddr/inicAddr results in command injection. It is possible to launch the attack remotely. The exploit has been released to the public and may be used for attacks. 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 · moderate confidence

Command injection vulnerability in Edimax BR-6675nD router firmware 1.12. The formHwSet function in the POST request handler /goform/formHwSet fails to sanitize user-supplied input in parameters (regDomain, ABandregDomain, nic0Addr, nic1Addr, wlanAddr, inicAddr), allowing remote attackers to inject arbitrary shell commands via crafted POST requests.

MitigationIf firmware update unavailable, restrict network access to the device's management interface via ACLs or disable remote administration; consider replacing affected hardware since vendor did not respond to disclosure.

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 device's web interface or check the device label/metadata to confirm the model is Edimax BR-6675nD
    Affected if The device is not an Edimax BR-6675nD model
  2. Check the firmware version
    Log into the web management interface and navigate to the firmware version information page, or use the device's administrative console to retrieve the installed firmware version
    Affected if The firmware version is not 1.12
  3. Verify the web management interface is accessible
    Attempt to access the device's HTTP/HTTPS web interface on the default management port (typically 80 or 443) to confirm the management service is running
    Affected if The web interface is not accessible from the network being tested
  4. Confirm the vulnerable endpoint is exposed
    Send a request to the /goform/formHwSet endpoint on the device to verify the wireless configuration form is available
    Affected if The /goform/formHwSet endpoint is not reachable or returns an error
  5. Check wireless configuration module accessibility
    In the web interface, navigate to the wireless settings section where hardware configuration parameters like regDomain, ABandregDomain, nic0Addr, nic1Addr, wlanAddr, and inicAddr can be accessed
    Affected if The wireless hardware configuration interface is not accessible or these parameters are not present

A user is affected if they are using an Edimax BR-6675nD device running firmware version 1.12 with the web management interface and wireless configuration module accessible on the 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

If firmware update unavailable, restrict network access to the device's management interface via ACLs or disable remote administration; consider replacing affected hardware since vendor did not respond to disclosure.

Recommended fix Moderate confidence
  1. Isolate the affected Edimax BR-6675nD device on a restricted network segment (VLAN) to limit exposure to untrusted actors
  2. Disable remote web management (HTTP/HTTPS access from WAN) if enabled on the router
  3. If the router's web interface is not required for legitimate operations, disable the HTTP service entirely via the device's administrative panel
  4. Implement network firewall rules to block external access to the device's management interface on ports 80/443
  5. Monitor network traffic for any attempts to access /goform/formHwSet as an indicator of reconnaissance or exploitation
  6. Consider replacing the affected device with a model that receives active security support
  7. If the device must remain in service, apply rate-limiting on upstream network equipment to reduce attack surface
Caveat No vendor-provided firmware patch is available; the device is End-of-Life with no security support from Edimax

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

Have this fixed 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-2026-9378 — 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-9378 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