CVE-2026-9343
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 weakness has been identified in Edimax EW-7438RPn up to 1.31. The affected element is the function formWpsStart of the file /goform/formWpsStart of the component webs. This manipulation of the argument pinCode causes os command injection. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be used for attacks. 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 · high confidenceOS command injection vulnerability in the Edimax EW-7438RPn Wi-Fi range extender's web interface. The formWpsStart function accepts user input through the pinCode parameter and passes it unsanitized to a system call, allowing remote attackers 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.
-
Identify device modelAccess the device web interface or check the device label/metadata to confirm the model is Edimax EW-7438RPnAffected if Device model is not EW-7438RPn, then not affected by this specific CVE
-
Check firmware versionLog into the device web interface (typically 192.168.1.1) and navigate to System Settings or Status page to view the firmware version; alternatively, inspect the firmware binary if extractedAffected if Firmware version is 1.31 or lower (any version up to and including 1.31)
-
Verify WPS functionality is enabledAccess the device web interface and check WPS settings under Wireless or Wi-Fi settings; look for WPS enable/disable toggleAffected if WPS is enabled - the command injection only affects the WPS PIN functionality
-
Confirm vulnerable endpoint is accessibleAttempt to access the URI /goform/formWpsStart on the device (HTTP POST with pinCode parameter); check if the web interface respondsAffected if The /goform/formWpsStart endpoint is accessible and responds to requests - indicates the vulnerable web service is running
-
Check network exposureDetermine if the device management interface is exposed to untrusted networks (WAN/internet) by reviewing router/firewall rules and port forwarding settingsAffected if Device web interface is accessible from untrusted networks (WAN-facing), increasing exploitation likelihood
User is affected if they have an Edimax EW-7438RPn device running firmware version 1.31 or lower with WPS enabled and the device web interface is 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 dataSince Edimax did not respond and no patch is available, recommend device replacement with a supported model. If immediate replacement is not feasible, isolate the device on a restricted network segment and disable WPS if possible to reduce attack surface.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9343 — 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-9343 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