dbcve.org
Di 7200gv2 FirmwareOperating system · Dlink

CVE-2021-46231

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 urlrd_opt.asp. This vulnerability allows attackers to execute arbitrary commands via the url_en 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 urlrd_opt.asp function. The url_en parameter is not properly sanitized, allowing attackers to inject and execute arbitrary OS commands with the privileges of the web server.

MitigationApply vendor firmware patch when available; until then, disable remote management interfaces, restrict access to the device's web interface to trusted IPs only via firewall rules, or replace the affected 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. Identify device model and firmware version
    Access the router's web administration panel and navigate to the System Status or Firmware Upgrade page to view the current firmware version. Alternatively, check the startup banner or system info page for the exact firmware build number.
    Affected if The firmware version is 21.04.09E1 or lower.
  2. Confirm web management interface is enabled
    Verify that the router's HTTP/HTTPS web interface is accessible. Attempt to reach the device's IP address on ports 80 or 443 from your administrative workstation.
    Affected if The web interface responds and is operational.
  3. Check remote management exposure
    Determine if the web interface is reachable from external networks (WAN side) or only from trusted LAN segments. Review firewall rules or access control settings on the device under the Administration or Access Control sections.
    Affected if The web management interface is accessible from untrusted networks or WAN interfaces.
  4. Identify the vulnerable endpoint
    Locate the urlrd_opt.asp file on the device's web server. This is typically found in the /asp/ or /cgi-bin/ directory structure of the firmware image.
    Affected if The urlrd_opt.asp file exists and accepts the url_en parameter without sanitization.

A user is affected if their D-Link DI-7200GV2 router runs firmware version 21.04.09E1 or below and the web management interface (containing the vulnerable urlrd_opt.asp function) is enabled 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 vendor firmware patch when available; until then, disable remote management interfaces, restrict access to the device's web interface to trusted IPs only via firewall rules, or replace the affected device.

Recommended fix Moderate confidence
  1. Check D-Link support announcements (supportannouncement.us.dlink.com) for any firmware updates specific to DI-7200GV2
  2. Verify if your device model is still within its official support lifecycle by consulting D-Link's product support pages
  3. Consider network segmentation to limit exposure of this device
  4. Implement firewall rules to restrict access to the device's web management interface to authorized IP addresses only
  5. If the device has reached end-of-life, replace it with a currently supported router that receives regular security updates
Caveat No vendor-provided patch or fixed firmware version identified for this vulnerability; the DI-7200GV2 may be end-of-life

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

Fix this in Di 7200gv2 Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-46231 — 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-46231 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