CVE-2026-12809
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 identified in Edimax BR-6478AC V2 1.23. Affected is the function wiz_5in1_redirect of the file /goform/wiz_5in1_redirect of the component POST Request Handler. Such manipulation of the argument newpass leads to command injection. The attack can be launched remotely. The exploit is publicly available and might 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 exists in the Edimax BR-6478AC V2 router firmware (v1.23) within the POST request handler for the /goform/wiz_5in1_redirect function. The 'newpass' parameter is not properly sanitized before being passed to a system call, allowing remote attackers to execute arbitrary shell commands on the device. The CVSS 6.3 suggests the attack may require some level of access or has limited scope.
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 modelLocate the router label or access the web interface to confirm the model is Edimax BR-6478AC V2Affected if Device model is Edimax BR-6478AC V2
-
Check firmware versionAccess the router admin panel (usually at 192.168.1.1) and look for the firmware version in the System or Status section, or check the Edimax support website for your device's firmware versionAffected if Firmware version is 1.23 or potentially earlier versions
-
Verify web interface accessibilityAttempt to access the router login page from the network. The vulnerability is in a POST handler, so the web server must be runningAffected if Web interface is accessible on the local network or (worse) exposed to external networks
-
Confirm the wiz_5in1_redirect endpoint existsSend a POST request to http://<router-ip>/goform/wiz_5in1_redirect with the 'newpass' parameter. If the device responds (even with an error), the endpoint is presentAffected if The /goform/wiz_5in1_redirect endpoint responds to requests, indicating the vulnerable function is enabled
-
Assess network exposureCheck router firewall settings and port forwards to determine if the web interface (port 80/443) is accessible from outside the local networkAffected if The router web interface is exposed to the internet or an untrusted network segment
You are affected if you have an Edimax BR-6478AC V2 router running firmware v1.23 with the web interface accessible and the /goform/wiz_5in1_redirect function enabled.
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 to disclosure, apply compensating controls: isolate the device on a restricted network segment, block external access to the web interface, and consider replacing the device with a supported model. If the feature is not required, disable it.
- 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-12809 — 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-12809 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