CVE Tools

CVE-2025-10123

D-Link DIR-823X set_static_leases sub_415028 command injection

Public exploit available. Not confirmed exploited in the wild yet. A vendor fix is available.

Published Updated Sources: CVE.org, NVD, BDU

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check whether you use a D-Link DIR-823X router and identify its firmware version; this issue affects DIR-823X firmware up to 250416.
  2. Verify whether your router management interface is reachable from the internet (for example via “remote management”, port forwarding, or any public-facing access).
  3. If it is reachable from the internet, block it at your firewall: allow only local/internal access to the router management ports.
  4. Disable any remote administration features and remove any port-forwarding rules that expose /goform endpoints to the internet.
  5. Update the router firmware to the vendor’s fixed remediation when available; if you cannot update immediately, rely on the firewall restrictions as the temporary control.

What it is

From the CVE record

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.

In plain language

Written by AI from the record

A remote command injection flaw in D-Link DIR-823X lets an attacker run commands on the router via the “set_static_leases” function, and there’s a public proof-of-concept—so typical small businesses should act now if the router is reachable from the internet.

CVE-2025-10123 is a remote command injection in D-Link DIR-823X (DIR-823X firmware) within /goform/set_static_leases (function sub_415028), triggered by manipulating the Hostname argument; public PoC exists and there has been sustained press/incident attention.

If you're affected

  • Router compromise
  • Network takeover
  • Traffic interception risk
  • Service disruption

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS92nd
Public exploit
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

3 sources with a proof of concept or module.

Exploit links, PoCs and Metasploit modules after sign-in
EPSS

4.7% chance of exploitation activity in the next 30 days, which ranks it in the 92nd percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

A public exploit existed 53 days before the patch.

  1. Patch availablerecord updated
  2. Public exploit / PoCsource: github-poc
  3. Publishedweakness classified, att&ck mapped

Affected products

Technical detail

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Scored 7.3 by NVD.

How it is reached

  • Attack Vector NetworkExploitable remotely over the network without any special conditions
  • Attack Complexity LowNo special conditions — the attack can be reliably reproduced
  • Privileges Required NoneNo authentication required — anyone can exploit this
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality LowSome restricted information is disclosed, but limited in scope
  • Integrity LowData modification is possible but limited in scope or consequence
  • Availability LowReduced performance or intermittent disruption of service

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for DIR-823X, not every advisory. This one: public exploit.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store