dbcve.org
Dir 818lw FirmwareOperating system · Dlink

CVE-2025-7553

HIGH · 7.2 CVSS v3.1 Published 2025-07-14
Fix available
A fix is available. Upgrade to 20191215 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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-818LW up to 20191215. This affects an unknown part of the component System Time Page. The manipulation of the argument NTP Server leads to os command injection. It is possible to initiate the attack remotely. The exploit has been disclosed to the public and may be used. 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

OS command injection vulnerability in D-Link DIR-818LW router's System Time Page. The NTP Server parameter is not properly sanitized before being passed to system shell, allowing remote attackers to inject arbitrary OS commands via the web interface.

MitigationDevice is End-of-Life and no longer supported by vendor. Replace with a currently supported router. If replacement is not possible, restrict all network access to the management interface and disable remote administration.

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 818lw FirmwareOperating system
Affected:< 20191215

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/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 device label on the router or log into the web interface and look for the model number in the status or management pages
    Affected if The device is not a D-Link DIR-818LW
  2. Check the firmware version
    Log into the router web interface, go to Status or System section, and locate the firmware version. Compare it to the affected version: any build date before 20191215
    Affected if Firmware version is earlier than the 20191215 build or shows a date prior to December 15, 2019
  3. Verify web management interface is accessible
    Attempt to access the router's web interface via its LAN IP address (typically 192.168.0.1) from within the network
    Affected if The web management interface is reachable and responds
  4. Confirm NTP configuration is accessible
    Log into the web interface and navigate to System Tools > Time Settings or similar section where NTP Server can be configured
    Affected if NTP Server configuration field exists and is accessible in the web interface

A user is affected if they own a D-Link DIR-818LW router running firmware dated before December 15, 2019, with the web management interface accessible and NTP settings available.

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 20191215 or later
Fixed in 20191215
Interim mitigation

Device is End-of-Life and no longer supported by vendor. Replace with a currently supported router. If replacement is not possible, restrict all network access to the management interface and disable remote administration.

Recommended fix Moderate confidence
  1. This vulnerability affects D-Link DIR-818LW firmware versions prior to 20191215
  2. The product is end-of-life and no longer supported by D-Link
  3. No vendor patch or firmware update is available for this vulnerability
  4. Consider network-level mitigations such as blocking external NTP access or placing the device behind a firewall
  5. If the device is critical and cannot be replaced, monitor for suspicious activity and restrict network access to trusted sources only
Caveat Device is end-of-life with no available firmware updates; replacement with a supported device is recommended

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

Fix this in Dir 818lw Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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