CVE-2026-9403
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-6675nD 1.12. The impacted element is the function formWlSiteSurvey of the file /goform/formWlSiteSurvey of the component POST Request Handler. This manipulation of the argument selSSID causes buffer overflow. The attack may be initiated remotely. The exploit has been publicly disclosed and may be utilized. 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 confidenceBuffer overflow vulnerability in Edimax BR-6675nD 1.12 wireless router's web management interface. The formWlSiteSurvey function in /goform/formWlSiteSurvey fails to properly validate the selSSID parameter length in POST requests, allowing an attacker to overflow a buffer with excessive input. This high-severity flaw is remotely exploitable and could potentially allow arbitrary code execution.
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 the router modelCheck the device label on the router or log into the web interface and look for the model name in the status or system information pageAffected if The device is not an Edimax BR-6675nD, then it is not affected by this specific CVE
-
Check the firmware versionLog into the router web interface and navigate to System Status or Firmware Upgrade page to view the current firmware version, or check the version displayed on the main status pageAffected if The installed firmware version is 1.12, the device is within the affected version range
-
Confirm web interface accessibilityAttempt to access the router web interface from a remote location or verify remote management settings in the administration or system setup section of the web interfaceAffected if Remote web management is enabled and accessible from untrusted networks, the vulnerability can be exploited remotely
-
Verify the vulnerable endpoint existsCheck if the router responds to requests at /goform/formWlSiteSurvey by accessing this path through the web interface or checking the firmware for this form handlerAffected if The /goform/formWlSiteSurvey endpoint is present and processes selSSID parameters, the buffer overflow condition can be triggered
You are affected if you own an Edimax BR-6675nD router running firmware version 1.12 with the web interface accessible (especially remotely) and the formWlSiteSurvey function 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 dataSince the vendor did not respond to disclosure and no patch is expected, restrict management interface access to local networks only, disable remote web management, or replace the end-of-life device with a currently supported router.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9403 — 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-9403 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