dbcve.org
Dir 816l FirmwareOperating system · Dlink

CVE-2025-9727

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-31
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
A weakness has been identified in D-Link DIR-816L 206b01. Affected by this issue is the function soapcgi_main of the file /soap.cgi. This manipulation of the argument service causes os command injection. Remote exploitation of the attack is possible. The exploit has been made available to the public and could be exploited. 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-816L router firmware 206b01. The soapcgi_main function in /soap.cgi fails to sanitize the service argument, allowing remote attackers to inject and execute arbitrary operating system commands. The vulnerability is exploitable remotely with CVSS 9.8 (Critical) and public exploits are available.

MitigationSince D-Link DIR-816L is end-of-life with no vendor patches, isolate the device behind a firewall restricting HTTP/HTTPS access, or replace with a supported device receiving security updates.

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 816l FirmwareOperating system
Affected:= 2.06b01

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 router label or access the web interface and look for the model number in the status or device info page
    Affected if The device is not a D-Link DIR-816L router
  2. Check the firmware version
    Access the router web interface, go to Status or System section, and locate the firmware version field. Alternatively, check the download file name if you have access to the firmware binary
    Affected if The firmware version is not 206b01 or 2.06b01
  3. Verify soap.cgi endpoint exists
    Attempt to access http://router_ip/soap.cgi or check the firmware file system for the presence of /soap.cgi
    Affected if The soap.cgi binary or endpoint does not exist on the device
  4. Assess network exposure
    Check if the router web interface (port 80 or 443) is exposed directly to the internet or an untrusted network
    Affected if The router management interface is reachable from untrusted networks without firewall restrictions

The device is affected only if it is a D-Link DIR-816L router running firmware version 206b01 (2.06b01) with the soap.cgi endpoint accessible, which allows remote command injection via the service argument.

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 D-Link DIR-816L is end-of-life with no vendor patches, isolate the device behind a firewall restricting HTTP/HTTPS access, or replace with a supported device receiving security updates.

Recommended fix High confidence
  1. This vulnerability affects D-Link DIR-816L firmware 2.06b01, which is explicitly stated as a product no longer supported by the maintainer.
  2. No vendor patch or firmware update is available for this end-of-life device.
  3. Replace the affected D-Link DIR-816L router with a currently supported model from D-Link or another vendor.
  4. If immediate replacement is not possible, place the device behind a properly configured firewall and restrict all external access to the device's management interfaces.
  5. Disable any exposed soap.cgi or remote management features if accessible from the internet.
  6. Monitor the network for any suspicious outbound connections from the device.
Caveat Device is end-of-life with no security updates available; replacement with a supported device is the only proper remediation

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

Fix this in Dir 816l Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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