CVE-2026-12806
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 has been found in Edimax BR-6478AC V2 1.23. The impacted element is the function formWlSiteSurvey of the file /goform/formWlSiteSurvey of the component POST Request Handler. The manipulation of the argument selSSID leads to buffer overflow. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may 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 · moderate confidenceA buffer overflow vulnerability exists in the Edimax BR-6478AC V2 firmware version 1.23 within the formWlSiteSurvey function of the POST request handler at /goform/formWlSiteSurvey. The selSSID parameter is not properly bounds-checked before use, allowing an attacker to overflow the buffer via a crafted POST request.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device modelCheck the device label on the Edimax BR-6478AC V2 unit, or log into the web interface and navigate to the system status or information page to confirm the model number.Affected if The device model is Edimax BR-6478AC V2 and the firmware version displays as 1.23.
-
Confirm firmware versionAccess the router web interface, typically at 192.168.0.1, and navigate to System > Firmware Upgrade or System Status to view the installed firmware version.Affected if The firmware version shown is exactly 1.23, matching the affected version listed in the CVE.
-
Verify web interface accessibilityAttempt to access the router web interface at /goform/formWlSiteSurvey via HTTP POST request, or confirm the router management web server is reachable on the local network.Affected if The router web management interface is accessible and the formWlSiteSurvey endpoint exists, indicating the vulnerable code path is present.
-
Confirm WiFi site survey feature existsLog into the router web interface and navigate to the Wireless settings section to verify the Site Survey or WiFi scanning functionality is present and enabled.Affected if The Wireless site survey feature is available and enabled on the device, meaning the vulnerable formWlSiteSurvey function can be invoked.
A user is affected if they own an Edimax BR-6478AC V2 router running firmware version 1.23 with the web interface and WiFi site survey feature accessible.
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 dataNo vendor patch is available as the vendor did not respond to disclosure; implement network segmentation to limit exposure, and consider replacing the end-of-life device since firmware updates are unlikely.
- Consultation4.0 h
- Implementation2.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,160.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12806 — 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-12806 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