dbcve.org
Dir 600l FirmwareOperating system · Dlink

CVE-2025-4350

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-06
Fix available
A fix is available. Upgrade to after 2.07b01 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
A vulnerability classified as critical was found in D-Link DIR-600L up to 2.07B01. This vulnerability affects the function wake_on_lan. The manipulation of the argument host leads to command injection. The attack can be initiated remotely. This vulnerability only affects products that are no longer supported by the maintainer.

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

The D-Link DIR-600L router (firmware up to 2.07B01) contains a command injection vulnerability in the wake_on_lan function. The 'host' parameter is not properly sanitized before being used in a system command, allowing an attacker to inject arbitrary shell commands by manipulating this input. The attack can be initiated remotely without authentication.

MitigationSince D-Link no longer supports the DIR-600L, no vendor patch is available. The device should be replaced with a currently supported model. If continued use is unavoidable, network segmentation and disabling remote administration access can reduce exposure, but this does not eliminate the vulnerability.

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
Dir 600l FirmwareOperating system
Affected:<= 2.07b01

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
    Access the router web interface or check the device label to confirm the model is D-Link DIR-600L
    Affected if The device is a D-Link DIR-600L router
  2. Check firmware version
    Log into the router web interface and navigate to the Status or Firmware Upgrade page to view the current firmware version
    Affected if Firmware version is 2.07B01 or lower
  3. Verify wake_on_lan feature exists
    Locate the wake_on_lan or WoL function in the router web interface (typically under Advanced or Networking settings)
    Affected if The wake_on_lan feature is present and accessible in the router interface
  4. Check remote administration access
    Inspect the router's remote management settings (often found under Advanced > Remote Management or similar) to determine if remote HTTP/HTTPS access is enabled
    Affected if Remote administration/WAN access is enabled, making the vulnerable wake_on_lan function accessible from the internet

A user is affected if they have a D-Link DIR-600L router running firmware version 2.07B01 or lower with the wake_on_lan feature accessible, especially if remote administration is enabled.

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 2.07b01
Interim mitigation

Since D-Link no longer supports the DIR-600L, no vendor patch is available. The device should be replaced with a currently supported model. If continued use is unavoidable, network segmentation and disabling remote administration access can reduce exposure, but this does not eliminate the vulnerability.

Recommended fix High confidence

Replace with a currently supported D-Link router or any vendor's current-generation router that receives active security updates

  1. 1. Discontinue use of the D-Link DIR-600L device as it has reached end-of-life and no longer receives security updates from the manufacturer.
  2. 2. Replace the affected device with a currently supported router that receives regular firmware security patches.
  3. 3. If immediate replacement is not possible, place the affected device in a separate network segment (VLAN) to limit potential attack surface.
  4. 4. Disable the wake_on_lan feature if accessible via the web interface to reduce attack vector.
  5. 5. Implement firewall rules to block external access to the device's management interface from untrusted networks.
  6. 6. Monitor network traffic for any suspicious activity targeting this device.
Caveat Hardware replacement required; the DIR-600L is end-of-life and will not receive patches for this critical vulnerability

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

Fix this in Dir 600l Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,800
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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