dbcve.org
Dir 605l FirmwareOperating system · Dlink

CVE-2025-4443

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
High EPSS 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-605L 2.13B01. It has been rated as critical. This issue affects the function sub_454F2C. The manipulation of the argument sysCmd leads to command injection. The attack may 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

A command injection vulnerability exists in D-Link DIR-605L firmware 2.13B01. The function sub_454F2C accepts user-supplied input through the sysCmd parameter without proper sanitization, allowing remote attackers to execute arbitrary operating system commands. The CVSS 9.8 indicates trivial exploitation without authentication.

MitigationThis vulnerability has no patch as the device is end-of-life. Recommended remediation is to replace affected devices with currently supported hardware. If immediate replacement is not feasible, network segmentation and firewall rules to block external access to the device's management interface should be implemented as a compensating control.

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 the device model
    Check the device label or access the web interface and look for the model number (DIR-605L) in the device info or status page
    Affected if The device is a D-Link DIR-605L router
  2. Check the firmware version
    Access the router's web management interface, navigate to the Status or System section, and look for the firmware version displayed. Alternatively, check the download file or upgrade page.
    Affected if The firmware version is exactly 2.13B01
  3. Verify sysCmd functionality is present
    Send an HTTP POST request to the router's web interface (typically at /goform/) with a sysCmd parameter. For example: POST /goform/ form with sysCmd=cat /etc/passwd
    Affected if The router responds to sysCmd parameter requests (even with an error, this indicates the function exists)
  4. Check if management interface is network-accessible
    From an external network host, attempt to reach the router's HTTP port (typically 80 or 443) using the router's public IP. Use: curl -v http://<router-ip>/
    Affected if The router's web management interface is reachable from untrusted networks (the vulnerability is remotely exploitable without authentication)

You are affected if you have a D-Link DIR-605L router running firmware version 2.13B01 with the web management interface network-accessible, as the command injection via sysCmd can be exploited remotely without authentication.

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

This vulnerability has no patch as the device is end-of-life. Recommended remediation is to replace affected devices with currently supported hardware. If immediate replacement is not feasible, network segmentation and firewall rules to block external access to the device's management interface should be implemented as a compensating control.

Recommended fix High confidence
  1. 1. Replace the D-Link DIR-605L router with a currently supported device. This model is end-of-life and no longer receives security updates from D-Link.
  2. 2. If immediate replacement is not possible, restrict network access to the device by placing it behind a firewall or NAT, limiting exposure to only trusted internal networks.
  3. 3. Disable any remote management features (web GUI access from WAN) if enabled.
  4. 4. Monitor the device for any signs of compromise.
  5. 5. As a long-term plan, migrate to a supported router that receives regular firmware security updates.
Caveat The DIR-605L is end-of-life with no further firmware releases; replacement with a supported device is required.

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
  • 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-4443 — 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-4443 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