CVE-2026-9361
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 1.12. This affects the function formAccept of the file /goform/formAccep of the component POST Request Handler. This manipulation of the argument submit-url causes command injection. The attack may be initiated remotely. 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 confidenceCommand injection vulnerability in Edimax EW-7438RPn 1.12 WiFi range extender's web interface. The formAccept function in /goform/formAccept does not properly sanitize the submit-url parameter, allowing remote attackers to inject arbitrary shell commands via crafted POST requests.
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 device administration interface or check the physical device label for the model number (Edimax EW-7438RPn)Affected if The device is an Edimax EW-7438RPn WiFi range extender
-
Determine the firmware versionLog into the web interface and navigate to System Status or Settings to view the firmware version, or check via telnet/SSH if enabledAffected if The firmware version is v1.12 or falls within the v1.x release line for this model
-
Verify the web interface is accessibleAttempt to reach the device web interface via its IP address on ports 80 or 443 from a trusted internal hostAffected if The web interface at /goform/formAccept is reachable over the network
-
Assess network exposure of the management interfaceCheck router/firewall rules to determine if the device web interface (ports 80/443) is exposed to untrusted networks such as the internet or guest WiFi segmentsAffected if The device web interface is accessible from untrusted networks (internet-facing or guest network segments)
The device is affected if it is an Edimax EW-7438RPn running firmware v1.12 (or v1.x) with its web interface accessible, since the command injection flaw in /goform/formAccept can be exploited remotely.
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, apply network segmentation to isolate the device, restrict administrative access to trusted IPs only, and consider replacing the device if no firmware patch becomes available. Monitor for indicators of compromise.
- Consultation4.0 h
- Implementation4.0 h
- Testing2.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,488.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-9361 — 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-9361 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