dbcve.org
Dir 605l FirmwareOperating system · Dlink

CVE-2025-4445

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 has been found in D-Link DIR-605L 2.13B01. Affected is the function wake_on_lan. The manipulation of the argument mac leads to command injection. It is possible to launch the attack remotely. The vendor was contacted early about this disclosure. 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

Command injection vulnerability in D-Link DIR-605L router's wake_on_lan function allows remote attackers to execute arbitrary commands via the unsanitized 'mac' argument. The vulnerability is exploitable remotely with CVSS 9.8 (critical), requiring only network access to the affected device.

MitigationSince the product is end-of-life and no longer supported by the vendor, replace the device with a currently supported router. If immediate replacement is not possible, isolate the device on a restricted network segment and disable the wake_on_lan feature if accessible.

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 605l FirmwareOperating system
Affected:= 2.13b01

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's web management interface or check the device label/sticker for the model number DIR-605L
    Affected if Device is a D-Link DIR-605L router
  2. Check firmware version
    Log into the router web interface and navigate to Status or Firmware Upgrade page to view the installed firmware version, or use the command 'cat /proc/version' or 'cat /etc/fw_info' via telnet/SSH if available
    Affected if Firmware version is 2.13B01
  3. Verify wake_on_lan functionality is present
    Access the router's web management interface and look for a Wake-on-LAN (WOL) feature, typically found under Advanced or Networking settings
    Affected if Wake-on-LAN feature is enabled and accessible on the device
  4. Assess management interface exposure
    Determine if the router's web interface (typically on ports 80/443) is reachable from untrusted networks such as the internet or guest networks
    Affected if The router's management interface is exposed to network segments outside the trusted local network

User is affected if they have a D-Link DIR-605L router running firmware 2.13B01 with the wake_on_lan feature accessible and the management interface reachable from untrusted networks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Since the product is end-of-life and no longer supported by the vendor, replace the device with a currently supported router. If immediate replacement is not possible, isolate the device on a restricted network segment and disable the wake_on_lan feature if accessible.

Recommended fix Moderate confidence
  1. This vulnerability affects D-Link DIR-605L firmware 2.13B01, which is an end-of-life (EOL) product no longer supported by D-Link.
  2. There is no official patch or firmware upgrade available from the vendor for this vulnerability.
  3. Consider replacing the affected device with a currently supported model from D-Link or another vendor.
  4. If replacement is not immediately possible, implement network segmentation to isolate the affected device from sensitive network segments.
  5. Disable the wake_on_lan (WOL) functionality if not required, to reduce the attack surface.
Caveat The DIR-605L is end-of-life with no vendor support; firmware upgrades are not available

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

Fix this in Dir 605l Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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