dbcve.org
Dir 823x FirmwareOperating system · Dlink

CVE-2026-1125

CRITICAL · 9.8 CVSS v3.1 Published 2026-01-18
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-823X 250416. Affected by this issue is the function sub_412E7C of the file /goform/set_wifidog_settings. Executing a manipulation of the argument wd_enable can lead to command injection. The attack can be executed remotely. The exploit has been made available to the public and could be used for attacks.

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 firmware (version 250416) within the /goform/set_wifidog_settings endpoint. The wd_enable parameter passed to function sub_412E7C is not properly sanitized before being used in system command execution, allowing remote attackers to inject arbitrary shell commands with root privileges.

MitigationIf available, apply vendor firmware updates. Otherwise, disable the WiFiDog captive portal feature through the router interface, disable remote web management, and restrict access to the device's administrative interface to trusted IPs only.

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

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 and firmware version
    Access the router's web administration interface or check via CLI/ssh if available. Navigate to System > Firmware or Status page to find the exact firmware version number.
    Affected if Firmware version is exactly 250126
  2. Confirm WiFiDog captive portal feature is enabled
    In the router web interface, look for WiFiDog or Captive Portal settings (typically under Wireless or Network settings). Check if the feature toggle is turned ON or enabled.
    Affected if WiFiDog captive portal feature is enabled on the device
  3. Check if remote web management is accessible
    Verify that the router's web administration interface is accessible from external/network interfaces (typically on port 80/443). Check Settings > Administration > Remote Management to see if it is enabled.
    Affected if Remote web management is enabled, making the vulnerable endpoint accessible from network
  4. Verify the vulnerable endpoint exists
    Check if the /goform/set_wifidog_settings URI is present and accessible on the device by attempting to access it or examining the firmware web binaries.
    Affected if The /goform/set_wifidog_settings endpoint is present and responds to requests

Device is affected if it is a D-Link DIR-823X router running firmware version 250126 with WiFiDog captive portal enabled and web management 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

If available, apply vendor firmware updates. Otherwise, disable the WiFiDog captive portal feature through the router interface, disable remote web management, and restrict access to the device's administrative interface to trusted IPs only.

Recommended fix Moderate confidence

Latest available DIR-823X firmware (check www.dlink.com for version beyond 250126)

  1. Check D-Link support site (www.dlink.com) for the latest DIR-823X firmware version
  2. Download the most recent firmware update available for the DIR-823X
  3. Review the firmware release notes to confirm the update addresses CVE-2026-1125
  4. Upload and install the firmware via the router's web administration interface
  5. After updating, verify the version number reflects the new firmware
  6. Confirm that the /goform/set_wifidog_settings endpoint no longer accepts malicious input for wd_enable parameter
Caveat Firmware updates may reset router configuration to defaults; back up current settings before upgrading

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

Fix this in Dir 823x Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,180
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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