dbcve.org
Dir 823x FirmwareOperating system · Dlink

CVE-2025-2717

HIGH · 7.2 CVSS v3.1 Published 2025-03-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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, which was classified as critical, has been found in D-Link DIR-823X 240126/240802. This issue affects the function sub_41710C of the file /goform/diag_nslookup of the component HTTP POST Request Handler. The manipulation of the argument target_addr leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed to the 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 · high confidence

OS command injection vulnerability in D-Link DIR-823G router's web interface. The diag_nslookup form handler (/goform/diag_nslookup) accepts user input through the target_addr parameter and passes it unsanitized to system(), allowing remote attackers to execute arbitrary shell commands by injecting metacharacters.

MitigationApply available firmware update from D-Link; if unavailable, disable remote web management, restrict admin interface to trusted IPs only, or replace the affected 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
Dir 823x FirmwareOperating system
Affected:= 240126= 240802

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 or access the web interface and look for the model number (DIR-823G) in the status or system information page
    Affected if Device is not a D-Link DIR-823G router
  2. Check the firmware version
    Access the router's web interface, go to Status or System section, and locate the firmware version information
    Affected if Firmware version is 240126 or 240802
  3. Verify web management is enabled
    In the router web interface, go to Settings > Administration or Management and check if the HTTP/HTTPS web management interface is enabled
    Affected if Web management interface is enabled and accessible from the network where attackers could reach it
  4. Confirm the vulnerable endpoint exists
    Attempt to access the URI /goform/diag_nslookup on the router (note: this is for verification only, not exploitation)
    Affected if The endpoint responds, indicating the vulnerable CGI handler is present

A user is affected if they have a D-Link DIR-823G router running firmware version 240126 or 240802 with the web interface enabled and accessible.

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

Apply available firmware update from D-Link; if unavailable, disable remote web management, restrict admin interface to trusted IPs only, or replace the affected device.

Recommended fix Moderate confidence

Latest DIR-823X firmware available from D-Link (check www.dlink.com for version number)

  1. 1. Visit D-Link's official support page for the DIR-823X at www.dlink.com to check for available firmware updates
  2. 2. Download the latest firmware version available from D-Link's official sources only
  3. 3. Access the router's web management interface and navigate to the firmware upgrade section
  4. 4. Upload and apply the new firmware following D-Link's documented upgrade procedure
  5. 5. After upgrading, verify the /goform/diag_nslookup function no longer accepts arbitrary command input
  6. 6. If no firmware update is available from D-Link, consider replacing the device with a currently supported model
Caveat Review D-Link release notes for any configuration reset requirements or feature changes after firmware update

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

Fix this in Dir 823x Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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