dbcve.org
Dir 110 FirmwareOperating system · Dlink

CVE-2018-25115

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-27
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
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
Multiple D-Link DIR-series routers, including DIR-110, DIR-412, DIR-600, DIR-610, DIR-615, DIR-645, and DIR-815 firmware version 1.03, contain a vulnerability in the service.cgi endpoint that allows remote attackers to execute arbitrary system commands without authentication. The flaw stems from improper input handling in the EVENT=CHECKFW parameter, which is passed directly to the system shell without sanitization. A crafted HTTP POST request can inject commands that are executed with root privileges, resulting in full device compromise. These router models are no longer supported at the time of assignment and affected version ranges may vary. Exploitation evidence was first observed by the Shadowserver Foundation on 2025-08-21 UTC.

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

This is an unauthenticated command injection vulnerability in the service.cgi endpoint of multiple D-Link DIR-series routers. The EVENT=CHECKFW parameter is passed directly to the system shell without sanitization, allowing attackers to inject arbitrary commands via crafted HTTP POST requests. Successful exploitation grants root-level code execution, enabling complete device compromise.

MitigationReplace end-of-life D-Link routers with supported models from vendors providing regular security updates. As an interim measure, restrict network access to the router's management interface using firewall rules or ACLs to prevent external attackers from reaching the service.cgi endpoint.

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 110 FirmwareOperating system
Affected:all versions
Dir 412 FirmwareOperating system
Affected:all versions
Dir 600 FirmwareOperating system
Affected:all versions
Dir 610 FirmwareOperating system
Affected:all versions
Dir 615 FirmwareOperating system
Affected:all versions
Dir 645 FirmwareOperating system
Affected:all versions
Dir 815 FirmwareOperating system
Affected:= 1.03

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 your D-Link router model
    Log into the router web interface and navigate to Status or System section to view the device model name and number, or check the physical device label
    Affected if The device model is one of: DIR-110, DIR-412, DIR-600, DIR-610, DIR-615, DIR-645, or DIR-815 (firmware version 1.03)
  2. Check the installed firmware version
    In the router web interface, go to Maintenance > Firmware Upgrade or System > Tools to view the current firmware version
    Affected if The firmware version is any version for DIR-110, DIR-412, DIR-600, DIR-610, DIR-615, DIR-645, or specifically version 1.03 for DIR-815
  3. Verify network exposure of the management interface
    Check your firewall or router configuration to determine if the router web interface (port 80/443) is accessible from external/WAN networks, or run a port scan from outside your network targeting the router IP
    Affected if The router management interface (including service.cgi) is directly accessible from untrusted networks such as the internet
  4. Test for vulnerability accessibility
    Attempt to access the service.cgi endpoint via HTTP POST from an external location, sending a request with EVENT=CHECKFW parameter (note: only do this in your own network with authorization)
    Affected if The device responds to requests to service.cgi with the EVENT parameter from outside the local network
  5. Check for signs of compromise
    Review router logs in Status > Log or System > Tools > Log for unexpected commands, suspicious HTTP POST requests to service.cgi, or unauthorized configuration changes
    Affected if Logs show unusual commands, POST requests to service.cgi from unknown IPs, or unexpected system behavior

You are affected if you own a D-Link DIR-110, DIR-412, DIR-600, DIR-610, DIR-615, DIR-645, or DIR-815 (firmware 1.03) router and its management interface is accessible from untrusted networks.

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

Replace end-of-life D-Link routers with supported models from vendors providing regular security updates. As an interim measure, restrict network access to the router's management interface using firewall rules or ACLs to prevent external attackers from reaching the service.cgi endpoint.

Recommended fix High confidence
  1. 1. Place the affected router behind a properly configured firewall or NAT gateway to restrict external access to the device's web management interface.
  2. 2. If remote management is not required, disable the web-based administration interface entirely through the router's settings.
  3. 3. If the router's web interface must be accessible, restrict access by IP address using the router's access control features if available.
  4. 4. Monitor network traffic for suspicious POST requests to /service.cgi with EVENT=CHECKFW parameters.
  5. 5. Consider replacing EOL (end-of-life) routers with currently supported models that receive security updates.
Caveat These D-Link DIR-series routers (DIR-110, DIR-412, DIR-600, DIR-610, DIR-615, DIR-645, DIR-815) are end-of-life and no longer supported by D-Link; no firmware updates are available.

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

Fix this in Dir 110 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 help mitigating

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-2018-25115 — 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-2018-25115 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