dbcve.org
Dir 823x FirmwareOperating system · Dlink

CVE-2025-10123

CRITICAL · 9.8 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to after 250416 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
A vulnerability was determined in D-Link DIR-823X up to 250416. Affected by this vulnerability is the function sub_415028 of the file /goform/set_static_leases. Executing manipulation of the argument Hostname can lead to command injection. The attack can be launched remotely. The exploit has been publicly disclosed and may be utilized.

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

A command injection vulnerability exists in D-Link DIR-823X routers (firmware up to 250416) in the /goform/set_static_leases endpoint. The Hostname parameter passed to function sub_415028 is not properly sanitized before being used in a system command, allowing an unauthenticated remote attacker to execute arbitrary operating system commands.

MitigationImmediately restrict access to the router's web administration interface from untrusted networks. If available, apply vendor firmware updates. Implement network segmentation to isolate affected devices and monitor for indicators of compromise.

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:<= 250416

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
    Access the router web interface or check device label to confirm it is a D-Link DIR-823G model
    Affected if Device is not a D-Link DIR-823G
  2. Check firmware version
    Log into the router web interface and navigate to Status or System settings to view the firmware version, or use telnet/SSH if enabled to run 'cat /proc/version' or similar command to retrieve firmware build date
    Affected if Firmware version/build date is 250416 or earlier
  3. Confirm web interface is accessible
    Attempt to access the router login page at the device IP address (typically 192.168.0.1) over HTTP
    Affected if Web interface is reachable from the network you are testing
  4. Verify set_static_leases endpoint exists
    Send a GET or POST request to /goform/set_static_leases on the router to confirm the endpoint is present and responds
    Affected if Endpoint responds (indicates web server with this form handler is enabled)

If the device is a D-Link DIR-823G with firmware version 250416 or earlier and its web interface is accessible on the network, the device is affected by this command injection 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 250416
Interim mitigation

Immediately restrict access to the router's web administration interface from untrusted networks. If available, apply vendor firmware updates. Implement network segmentation to isolate affected devices and monitor for indicators of compromise.

Recommended fix Low confidence
  1. 1. Check D-Link's official support website (www.dlink.com) for any available firmware updates for the DIR-823X device.
  2. 2. If no firmware update is available, implement network-level mitigations:
  3. a. Disable the device's web management interface from WAN/remote access
  4. b. Place the device in a restricted network segment/VLAN
  5. c. Implement firewall rules to limit access to the device's management ports
  6. 3. Monitor D-Link security advisories for future patches.
  7. 4. Consider replacing the affected device with a currently supported model if no patch becomes available.

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

Fix this in Dir 823x Firmware Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
36.0 hours of engineering $6,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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