CVE-2026-0732
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 D-Link DI-8200G 17.12.20A1. This affects an unknown function of the file /upgrade_filter.asp. The manipulation of the argument path results in command injection. The attack may be performed from remote. The exploit has been made public and could be used.
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 confidenceA command injection vulnerability exists in D-Link DI-8200G router firmware 17.12.20A1. The /upgrade_filter.asp page fails to properly sanitize the 'path' parameter, allowing remote attackers to inject and execute arbitrary OS commands. This is a critical pre-authentication flaw with publicly available exploits.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 17.12.20a1CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Verify the D-Link DI-8200G firmware versionAccess the router's web administration interface and navigate to the System or Status section to view the firmware version. Alternatively, check the version displayed on the device label or obtained via SNMP or the router's web API if available.Affected if The installed firmware version is exactly 17.12.20a1 (case-insensitive match)
-
Confirm the /upgrade_filter.asp endpoint existsAttempt to access the URL 'http://[device-ip]/upgrade_filter.asp' using a web browser or curl command. A 200 OK response or the page loading indicates the endpoint is present.Affected if The upgrade_filter.asp page is accessible on the device (the page must exist for the vulnerability to be exploitable)
-
Check if remote management is enabledIn the router's web interface, locate the 'Remote Management' or 'Remote Access' settings (usually under Administration, Security, or Access Control). Verify whether remote administration from external IP addresses is permitted.Affected if Remote management or remote administration access from WAN/outside networks is enabled, allowing unauthenticated attackers to reach the vulnerable endpoint
You are affected if your D-Link DI-8200G runs firmware version 17.12.20a1 AND the /upgrade_filter.asp endpoint is accessible, especially if remote management is 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 dataImmediately restrict network access to the device's management interface, contact D-Link for available firmware patches, and if no patch exists, implement network segmentation or replace the device to eliminate this critical attack vector.
- Consultation3.0 h
- Implementation8.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 $4,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0732 — 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-0732 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