CVE-2026-12807
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 vulnerability was found in Edimax BR-6478AC V2 1.23. This affects the function setWAN of the file /goform/setWAN of the component POST Request Handler. The manipulation of the argument pppUserName/pptpUserName/L2TPUserName results in command injection. It is possible to launch the attack remotely. The exploit has been made public and could 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 confidenceA command injection vulnerability in the Edimax BR-6478AC V2 (firmware 1.23) allows remote attackers to execute arbitrary OS commands via the /goform/setWAN POST request handler by injecting commands into the pppUserName, pptpUserName, or L2TPUserName parameters used in the setWAN function.
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 model and firmware versionAccess the Edimax BR-6478AC V2 web management interface (typically at 192.168.2.1) and check the firmware version displayed in the system status or administration settings. Alternatively, check via telnet or SSH if enabled.Affected if The device model is Edimax BR-6478AC V2 and the firmware version is 1.23.
-
Confirm web interface is activeVerify the device's web management interface is reachable over HTTP/HTTPS on the local network by accessing the device's IP address in a browser.Affected if The web interface responds and is accessible.
-
Verify WAN configuration functionality existsNavigate to the WAN settings page in the web interface and confirm that PPPoE, PPTP, or L2TP connection options are available and configurable.Affected if WAN settings allow configuration of pppUserName, pptpUserName, or L2TPUserName parameters.
-
Check network exposure of management interfaceDetermine if the web management interface is exposed to untrusted networks (such as directly to the internet or DMZ) by reviewing firewall rules, port forwarding configurations, or network segmentation.Affected if The web management interface (port 80/443) is accessible from untrusted networks or the internet.
The environment is affected if the Edimax BR-6478AC V2 is running firmware 1.23 and its web management interface is network-accessible, allowing injection into the WAN username parameters.
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 is unresponsive, immediately restrict web management interface access via network ACLs or firewall rules, or isolate the device on a separate VLAN. Check Edimax support for firmware updates or consider replacing the device if no patch is available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-12807 — 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-12807 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