dbcve.org
Dir 619l FirmwareOperating system · Dlink

CVE-2025-4451

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 has been found in D-Link DIR-619L 2.04B04 and classified as critical. Affected by this vulnerability is the function formSetWAN_Wizard52. The manipulation of the argument curTime leads to buffer overflow. The attack can be launched 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 · moderate confidence

Buffer overflow vulnerability in D-Link DIR-619L firmware 2.04B04 in the formSetWAN_Wizard52 function allows remote attackers to overflow the curTime argument, potentially enabling remote code execution given the critical 9.8 CVSS score.

MitigationSince the product is no longer supported, replace the affected D-Link DIR-619L router with a currently supported device; if replacement is not immediately feasible, restrict network access to the device's management interface using firewall rules or VLAN segmentation to prevent remote exploitation.

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 the router model
    Locate the device label on the router physical chassis or check the device information page in the web management interface to confirm the model is D-Link DIR-619L
    Affected if The device is a D-Link DIR-619L router
  2. Determine the installed firmware version
    Access the router web interface and navigate to the Status or Firmware Upgrade section to view the current firmware version, or use the router's CLI if available
    Affected if The firmware version is exactly 2.04B04
  3. Verify the web management interface is enabled
    Check the router's administration settings to confirm the HTTP/HTTPS web interface is turned on, since the vulnerable formSetWAN_Wizard52 function is accessed via this web interface
    Affected if The web management interface is enabled
  4. Assess exposure of the management interface
    Review network configuration to determine if the router's web interface is accessible from external networks or the internet, as this vulnerability allows remote exploitation
    Affected if The management interface is reachable from untrusted network segments

A user is affected if they are running D-Link DIR-619L firmware version 2.04B04 with the web management interface enabled and exposed to network access where the attacker can send requests to the formSetWAN_Wizard52 function.

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 no longer supported, replace the affected D-Link DIR-619L router with a currently supported device; if replacement is not immediately feasible, restrict network access to the device's management interface using firewall rules or VLAN segmentation to prevent remote exploitation.

Recommended fix High confidence
  1. This vulnerability affects D-Link DIR-619L firmware 2.04b04, which is a product line that D-Link no longer supports.
  2. There is no officially released patch, firmware update, or upgrade path available from D-Link for this specific vulnerability.
  3. Consider replacing the end-of-life DIR-619L router with a currently supported model that receives regular security updates.
  4. If replacement is not immediately possible, minimize exposure by placing the device behind a properly configured firewall, disabling remote management interfaces from the internet, and monitoring for suspicious activity.
Caveat This product is end-of-life with no vendor support; no firmware updates will be released.

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

Fix this in Dir 619l Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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