CVE-2026-7684
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-6428nC up to 1.16. This impacts an unknown function of the file /goform/setWAN. Such manipulation of the argument pptpDfGateway leads to buffer overflow. The attack can be launched 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 confidenceBuffer overflow vulnerability in Edimax BR-6428nC routers (firmware up to v1.16) in the /goform/setWAN web interface function. The pptpDfGateway parameter is not properly bounds-checked, allowing an attacker to overflow a buffer via crafted input. This can be exploited remotely without authentication.
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 device modelAccess the router's web administration interface and look for the model number (typically displayed on the login page, in the header, or under Status/System information). Look for 'BR-6428nC' or 'Edimax' branding.Affected if The device is NOT an Edimax BR-6428nC router.
-
Check the firmware versionIn the router's web interface, navigate to Status or System settings and locate the firmware version field. Compare it to v1.16.Affected if The firmware version is v1.16 or lower.
-
Verify the web interface is accessibleAttempt to access the router's web interface on the local network (typically http://192.168.1.1 or similar). Confirm the /goform/setWAN endpoint responds.Affected if The router's web interface with /goform/setWAN is accessible from your network.
-
Check if PPTP WAN is configurableIn the router's web interface under WAN or Internet settings, look for PPTP configuration options. The vulnerable parameter is 'pptpDfGateway' which relates to PPTP Default Gateway settings.Affected if PPTP WAN settings are present and configurable in the router's interface.
You are affected if you have an Edimax BR-6428nC router running firmware v1.16 or lower, with its web interface accessible, and the router exposes PPTP WAN configuration options.
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 is unresponsive to disclosure, mitigate by restricting network access to the router's management interface, upgrading to a newer model if available, or replacing with an actively supported device. If PPTP is enabled, disable it as a temporary measure.
- Consultation6.0 h
- Implementation8.0 h
- Testing4.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 $5,760.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-7684 — 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-7684 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