A weakness has been identified in Edimax EW-7438RPn 1.31. This impacts the function formAccept of the file /goform/formAccept. Executing a manipulation of the argument submit-url can lead to stack-based buffer overflow. It is possible to launch the attack 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.
CVE-2026-9460 is a critical memory corruption issue in Edimax EW-7438RPn firmware 1.31. A flaw in the device web handling path can let an authenticated remote attacker crash or potentially take control of the device. A public proof of concept exists, but the supplied sources do not show confirmed active exploitation.
Executive priority
Treat this as urgent for any deployed EW-7438RPn 1.31 device, especially if management access is exposed. Prioritize isolation and vendor guidance because public exploit information exists and no source in the bundle names a fixed version.
Technical view
The vulnerability affects /goform/formAccept in Edimax EW-7438RPn 1.31. Manipulating the submit-url argument can trigger a stack-based buffer overflow, mapped to CWE-119 and CWE-121. The CVSS v2 vector is AV:N/AC:L/Au:S/C:C/I:C/A:C, indicating network reachability, low complexity, required authentication, and full impact.
Likely exposure
Exposure is limited to Edimax EW-7438RPn devices running version 1.31 where the web management interface is reachable by an authenticated user. Internet-exposed or broadly reachable management interfaces are the highest concern.
Exploitation context
VulDB reports that exploit material has been made public and could be used for attacks. The source bundle does not include KEV listing or other evidence of active exploitation. The vendor was reportedly contacted but did not respond, and no patch is named in the supplied sources.
Researcher notes
Evidence supports a remotely reachable, authenticated stack overflow in submit-url handling. Public exploit availability is reported, but active exploitation is not confirmed. Patch status is unclear because the vendor reportedly did not respond. Avoid assuming affected firmware beyond version 1.31 from the supplied data.
Based on public source material and reviewed before publication.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-119: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve
time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
4CVSS vectors
6Timeline events
0ADP providers
5Source links
CVSS vector scores
4 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present,
the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-119 · source CWE mapping
Improper Restriction of Operations within the Bounds of a Memory Buffer
Improper Restriction of Operations within the Bounds of a Memory Buffer represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Stack-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.