Dir 619l FirmwareOperating system · Dlink

CVE-2025-4454

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 was found in D-Link DIR-619L 2.04B04. It has been declared as critical. This vulnerability affects the function wake_on_lan. The manipulation of the argument mac leads to command injection. The attack can be initiated 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

The D-Link DIR-619L router firmware 2.04B04 contains a command injection vulnerability in the wake_on_lan function where user-supplied MAC address input is improperly sanitized before being passed to system shell commands, allowing arbitrary command execution with root privileges.

MitigationSince the affected device is end-of-life and no longer supported by the vendor, replace the device with a currently supported model. If replacement is not immediately feasible, disable the wake-on-LAN feature, restrict management interface access to trusted IPs via firewall rules, and isolate the device on a restricted network segment.

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 619l FirmwareOperating system
Affected:= 2.04b04

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
    Log into the router web interface or check the device label to confirm the model is D-Link DIR-619L
    Affected if Device model is D-Link DIR-619L
  2. Check firmware version
    In the router web interface, navigate to Status or System Info section to view the firmware version. The affected version is 2.04b04
    Affected if Firmware version is 2.04b04
  3. Verify wake-on-LAN feature exists
    In the router web interface, look for a Wake-on-LAN (WoL) settings page, usually under Advanced or Network Settings
    Affected if Wake-on-LAN feature is present and accessible in the management interface
  4. Confirm management interface accessibility
    Check if the router admin interface is reachable over the network (HTTP/HTTPS on ports 80 or 443)
    Affected if Router management interface is accessible from the network

You are affected if you have a D-Link DIR-619L router running firmware version 2.04b04 and the wake-on-LAN feature is accessible through the web management interface.

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 affected device is end-of-life and no longer supported by the vendor, replace the device with a currently supported model. If replacement is not immediately feasible, disable the wake-on-LAN feature, restrict management interface access to trusted IPs via firewall rules, and isolate the device on a restricted network segment.

Recommended fix High confidence
  1. This D-Link DIR-619L router is end-of-life and no longer supported by the vendor.
  2. There is no available firmware patch or upgrade path for this vulnerability.
  3. Replace the affected D-Link DIR-619L router with a currently supported device from D-Link or another vendor.
  4. If immediate replacement is not possible, isolate the device on a restricted network segment (VLAN) with strict firewall rules to limit exposure.
  5. Disable the Wake-on-LAN feature if not required to reduce the attack surface.
Caveat No upgrade path available as the product is end-of-life and no longer supported by D-Link

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

Fix this in Dir 619l Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-4454 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