dbcve.org
InjectionWeakness · CWE-74

CVE-2026-10127

MEDIUM · 6.3 CVSS v3.1 Published 2026-05-30
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 weakness has been identified in Edimax BR-6478AC 1.23. This affects the function formStaDrvSetup of the file /goform/formStaDrvSetup of the component POST Request Handler. This manipulation of the argument rootAPmac causes command injection. The attack may be initiated remotely. The exploit has been made available to the public and could be used for attacks.

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

The Edimax BR-6478AC v1.23 wireless router has a command injection vulnerability in its web interface POST handler. The formStaDrvSetup function in /goform/formStaDrvSetup fails to sanitize the rootAPmac parameter before passing it to a system call, allowing remote attackers to execute arbitrary commands via crafted HTTP POST requests.

MitigationApply any vendor-supplied firmware update for BR-6478AC v1.23; if unavailable, consider network segmentation to restrict access to the router's web management interface or disable the affected functionality.

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 device model
    Access router web interface or check device label to confirm model is Edimax BR-6478AC
    Affected if Device model is Edimax BR-6478AC
  2. Check firmware version
    Navigate to router admin panel (typically 192.168.0.1) and locate firmware version in System Status or Firmware Upgrade section; or check via telnet/SSH if enabled
    Affected if Firmware version is 1.23
  3. Verify web interface accessibility
    Attempt to access http://[router-ip]/goform/formStaDrvSetup via HTTP POST request; check if the endpoint responds
    Affected if Web interface is reachable and the /goform/formStaDrvSetup endpoint exists and accepts requests
  4. Confirm wireless station feature is enabled
    Check router wireless settings for client/station mode (StaDrv) configuration; this function handles wireless client driver setup
    Affected if Wireless client/station functionality is enabled in router settings

User is affected if they have an Edimax BR-6478AC router running firmware version 1.23 with the web interface accessible and wireless station/client feature enabled, as the rootAPmac parameter in /goform/formStaDrvSetup can be exploited for command injection.

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

Apply any vendor-supplied firmware update for BR-6478AC v1.23; if unavailable, consider network segmentation to restrict access to the router's web management interface or disable the affected functionality.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,380
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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