dbcve.org
Dns 343 FirmwareOperating system · Dlink

CVE-2018-25120

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-29
Fix available
A fix is available. Upgrade to after 1.0.5 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
D-Link DNS-343 ShareCenter devices running firmware versions up to and including 1.05 contain a command injection vulnerability in the Mail Test functionality. The web maintenance script posts to the internal goForm endpoint '/goform/Mail_Test' and uses several form parameters directly in a call to a system email utility without proper input validation. An unauthenticated remote attacker can supply crafted form data that injects shell commands, resulting in execution as root on the device. NOTE: The DNS-343 product line has been declared end-of-life.

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

Unauthenticated command injection vulnerability in D-Link DNS-343 ShareCenter devices. The Mail Test functionality at '/goform/Mail_Test' endpoint passes user-supplied form parameters directly to a system email utility without input validation, allowing shell command injection with root privileges.

MitigationSince the device is end-of-life with no available patch, immediate mitigation requires network isolation (firewall/segmentation) to block unauthorized access to the device's web interface, or replacement with a supported device.

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
Dns 343 FirmwareOperating system
Affected:<= 1.0.5

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 device model
    Locate the device model number on the physical device label or check the web interface login page for the D-Link DNS-343 designation
    Affected if The device is NOT a D-Link DNS-343 ShareCenter
  2. Check firmware version
    Access the device web interface, navigate to the System/Status section to view the firmware version, or check the release notes/package file if you have firmware binary access
    Affected if Firmware version is greater than 1.0.5 (the device is patched) or the version cannot be determined
  3. Determine web interface exposure
    Check if the device web interface (HTTP/HTTPS on ports 80/443 or custom port) is reachable from network segments other than a dedicated management VLAN
    Affected if The web interface is accessible from untrusted networks without firewall filtering
  4. Verify Mail Test endpoint accessibility
    Attempt to access or send a request to /goform/Mail_Test endpoint (no authentication required per CVE description)
    Affected if The endpoint responds and accepts input without requiring authentication

A D-Link DNS-343 device running firmware version 1.0.5 or lower with its web interface exposed to network access is affected by this vulnerability.

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 1.0.5
Interim mitigation

Since the device is end-of-life with no available patch, immediate mitigation requires network isolation (firewall/segmentation) to block unauthorized access to the device's web interface, or replacement with a supported device.

Recommended fix High confidence
  1. Isolate the D-Link DNS-343 device on a restricted network segment to limit exposure to potential attackers.
  2. If the device is no longer needed, decommission it and replace with a supported alternative.
  3. If the device must remain in service, disable or block access to the web interface from untrusted networks using firewall rules.
  4. Monitor network traffic for signs of exploitation attempts targeting the /goform/Mail_Test endpoint.
  5. Consider implementing network intrusion detection to identify attempts to exploit command injection vulnerabilities.
Caveat The D-Link DNS-343 product line has been declared end-of-life with no further firmware updates. There is no available upgrade path from the vendor.

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

Fix this in Dns 343 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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