dbcve.org
Di 7200gv2 FirmwareOperating system · Dlink

CVE-2021-46226

CRITICAL · 9.8 CVSS v3.1 Published 2022-02-04
Fix available
A fix is available. Upgrade to after 21.04.09e1 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
D-Link device DI-7200GV2.E1 v21.04.09E1 was discovered to contain a command injection vulnerability in the function wget_test.asp. This vulnerability allows attackers to execute arbitrary commands via the url parameter.

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 confidence

D-Link DI-7200GV2.E1 router firmware v21.04.09E1 contains a command injection vulnerability in the wget_test.asp function. The url parameter is passed unsanitized to a system call (likely wget), allowing attackers to inject arbitrary shell commands and achieve full device compromise.

MitigationApply available firmware patches; if none exists, disable the vulnerable wget_test.asp function, restrict administrative interface access to trusted networks, or replace the device.

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
Di 7200gv2 FirmwareOperating system
Affected:<= 21.04.09e1

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm device is D-Link DI-7200GV2
    Identify the exact router model by checking the device label or logging into the web interface and viewing the device status page
    Affected if The device is a D-Link DI-7200GV2 or DI-7200GV2.E1 model
  2. Check firmware version
    In the router web interface, navigate to Status or System Info page to view the firmware version, or check via CLI if accessible
    Affected if Firmware version is 21.04.09E1 or any version prior to it (earlier versions)
  3. Verify wget_test.asp exists
    Attempt to access the URL path /wget_test.asp on the router's web interface using a browser (authentication may be required), or check the web server filesystem if you have terminal access
    Affected if The wget_test.asp page responds or the file exists in the web directory
  4. Assess administrative interface exposure
    Review the router's firewall settings and WAN access configuration to determine if the web management interface is reachable from external networks
    Affected if The router's administrative web interface (port 80/443) is accessible from untrusted or internet-facing networks

The device is affected if it is a D-Link DI-7200GV2 with firmware version 21.04.09E1 or lower, and the wget_test.asp function is present and accessible.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 21.04.09e1
Interim mitigation

Apply available firmware patches; if none exists, disable the vulnerable wget_test.asp function, restrict administrative interface access to trusted networks, or replace the device.

Recommended fix Moderate confidence

D-Link DI-7200GV2 firmware version > 21.04.09E1 (check D-Link support for latest available secure version)

  1. 1. Visit the official D-Link support page at www.dlink.com and navigate to the product support section for the DI-7200GV2 model.
  2. 2. Download the latest available firmware version for the DI-7200GV2 (firmware versions higher than 21.04.09E1 may contain the security fix).
  3. 3. Access the device web management interface through a secure, trusted network connection.
  4. 4. Navigate to the firmware upgrade section in the administration settings.
  5. 5. Upload and apply the new firmware version, following the on-screen instructions.
  6. 6. After the upgrade completes, verify the wget_test.asp function is no longer vulnerable by confirming the fix is included in the release notes or by testing that command injection is no longer possible.
  7. 7. If no newer firmware is available from D-Link, consider implementing network-level mitigations such as restricting access to the device management interface to trusted IP addresses only, or placing the device behind a firewall.
Caveat Firmware upgrades may reset device configuration to defaults; backup current configuration before upgrading and reapply after upgrade.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Di 7200gv2 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-46226 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-46226 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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