CVE-2026-9297
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 security vulnerability has been detected in Edimax BR-6428NS 1.10. Affected is the function formWlbasic of the file /goform/formWlbasic of the component POST Request Handler. The manipulation of the argument repeaterSSID leads to command injection. The attack may be initiated remotely. The exploit has been disclosed publicly 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 confidenceCommand injection vulnerability in Edimax BR-6428NS router firmware version 1.10 allows remote attackers to execute arbitrary OS commands via the repeaterSSID parameter in the /goform/formWlbasic POST request handler. The formWlbasic function fails to sanitize user input before passing it to system shell 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
- 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.
-
Identify the device modelAccess the router's web management interface and locate the device information page, or check the device label. Look for the model number 'BR-6428NS'.Affected if The device is an Edimax BR-6428NS router.
-
Check the firmware versionIn the router's web UI, navigate to Status or System Settings to view the firmware version. For CLI access, log in via telnet or SSH if enabled and run 'cat /proc/version' or check /etc/version file.Affected if The firmware version is 1.10 or falls within the 1.x range without confirmed patching.
-
Verify wireless repeater functionality is enabledIn the web UI, go to Wireless Settings or Repeater/Range Extender settings. Check if the repeater mode or universal repeater feature is configured with an SSID entered in the repeaterSSID field.Affected if The wireless repeater/repeater SSID field contains a value or is configured to connect to another AP.
-
Confirm the vulnerable endpoint is accessibleSend a POST request to http://<router_ip>/goform/formWlbasic with a test parameter (ensure you have authorization). The endpoint responds if the wireless configuration page is accessible.Affected if The /goform/formWlbasic endpoint responds to POST requests, indicating the vulnerable handler exists.
You are affected if you are running an Edimax BR-6428NS with firmware 1.10 and have the wireless repeater functionality enabled or configured on the device.
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 any vendor firmware update when available; until then, disable remote administration interfaces or restrict access to trusted networks to mitigate remote exploitation of this command injection flaw.
- Consultation6.0 h
- Implementation12.0 h
- Testing8.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 $8,448.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9297 — 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-9297 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