CVE-2026-10166
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 · uneditedA vulnerability was determined in Edimax BR-6478AC 1.23. The affected element is the function formWlbasic of the file /goform/formWlbasic of the component POST Request Handler. This manipulation of the argument rootAPmac causes command injection. The attack is possible to be carried out remotely. The exploit has been publicly disclosed and may be utilized.
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 confidenceThe Edimax BR-6478AC router firmware version 1.23 contains a command injection vulnerability in the POST request handler at /goform/formWlbasic. The formWlbasic function fails to sanitize the rootAPmac parameter before passing it to system commands, allowing an authenticated attacker to execute arbitrary shell commands on the device.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm router model is Edimax BR-6478ACCheck the device label on the router hardware or log into the web interface and locate the model number typically displayed on the status or overview pageAffected if The device is not an Edimax BR-6478AC router, then this specific CVE does not apply
-
Identify the installed firmware versionLog into the router web interface and navigate to the Administration or System Settings section to view the firmware version; alternatively, check the version displayed on the device status pageAffected if The firmware version is 1.23 exactly, or falls within the affected range around version 1.23 for this model
-
Verify the web management interface is accessibleAttempt to access the router web interface over HTTP/HTTPS on the local network; confirm the /goform/formWlbasic endpoint exists by checking if the wireless basic settings page loadsAffected if The web interface is exposed and the formWlbasic handler is present, which is required for the vulnerable code path to be reachable
-
Check if wireless basic settings with rootAPmac parameter are configurableNavigate to the wireless basic settings page in the web interface where the rootAPmac parameter would be used for access point configurationAffected if The wireless basic settings form with rootAPmac parameter is available and functional, meaning the vulnerable code path can be triggered
The environment is affected if the device is an Edimax BR-6478AC router running firmware version 1.23 with its web management interface accessible and the wireless basic settings (rootAPmac parameter) feature enabled.
Generated from the published advisory. Verify against your own configuration.
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 dataApply vendor firmware updates when available; alternatively, restrict access to the router's web management interface to trusted IP addresses or disable remote administration.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2026-10166 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-10166 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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