dbcve.org
Dir 868l B1 FirmwareOperating system · Dlink

CVE-2025-14659

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-14
Fix available
A fix is available. Upgrade to after 203b03 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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 detected in D-Link DIR-860LB1 and DIR-868LB1 203b01/203b03. Affected is an unknown function of the component DHCP Daemon. The manipulation of the argument Hostname results in command injection. It is possible to launch the attack remotely. The exploit is now public and may be used.

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

A command injection vulnerability exists in the DHCP daemon of D-Link DIR-860LB1 and DIR-868LB1 routers (firmware 203b01/203b03). The vulnerability allows remote attackers to inject arbitrary commands through the Hostname argument in DHCP requests, achieving CVSS 9.8 critical severity due to the trivial exploitability nature of command injection and the exposed network attack surface.

MitigationContact D-Link for available firmware updates; if no patch exists, replace affected devices with supported hardware and implement network segmentation to isolate legacy devices.

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 868l B1 FirmwareOperating system
Affected:<= 203b01
Dir 860l B1 FirmwareOperating system
Affected:<= 203b03

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
    Check the product label on the device or log into the router admin web interface and look for the model number in the status or system information page
    Affected if The device is not a D-Link DIR-860LB1 or DIR-868LB1, then it is not affected by this specific CVE
  2. Check the installed firmware version
    In the router admin interface, go to Status or System Settings and locate the firmware version field. Compare this version number against the affected ranges: DIR-868LB1 <= 203b01, DIR-860LB1 <= 203b03
    Affected if The firmware version falls within or below the affected ranges for your model
  3. Verify DHCP service accessibility
    From a computer on the same network, use a network scanner or nmap to check if UDP port 67/68 (DHCP) is open and reachable from network segments that contain untrusted devices
    Affected if The DHCP service is exposed to network segments with untrusted or internet-facing devices, increasing exploitability

You are affected if you own a DIR-860LB1 or DIR-868LB1 router running firmware at or below the specified version limits and the DHCP service is accessible from untrusted network segments.

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 203b03
Interim mitigation

Contact D-Link for available firmware updates; if no patch exists, replace affected devices with supported hardware and implement network segmentation to isolate legacy devices.

Recommended fix Moderate confidence
  1. 1. Immediately isolate affected devices (DIR-860LB1 and DIR-868LB1) from sensitive network segments using VLANs or network segmentation.
  2. 2. If the DHCP server function is not required, disable it on the affected devices.
  3. 3. Implement network-level filtering to restrict DHCP traffic to authorized management interfaces only.
  4. 4. Monitor for signs of compromise, particularly unexpected DHCP traffic patterns or unauthorized device enrollment.
  5. 5. Replace affected devices with currently-supported hardware that receives security updates. D-Link has historically not provided long-term firmware support for these legacy devices.
Caveat No firmware fix is available from D-Link for these end-of-life devices; the listed firmware versions (203b01/203b03) are the latest for these models and contain the vulnerability.

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

Fix this in Dir 868l B1 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing3.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,050
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,880.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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