dbcve.org
Dir X3260 FirmwareOperating system · Dlink

CVE-2023-44421

HIGH · 8.0 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.04b01 or later.
See remediation →
82/100
Remediation priority · High
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 DIR-X3260 SetTriggerPPPoEValidate Username Command Injection Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of D-Link DIR-X3260 routers. Although authentication is required to exploit this vulnerability, the existing authentication mechanism can be bypassed. The specific flaw exists within the prog.cgi program, which handles HNAP requests made to the lighttpd webserver listening on TCP ports 80 and 443. The issue results from the lack of proper validation of a user-supplied string before using it to execute a system call. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-21101.

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

Command injection vulnerability in D-Link DIR-X3260 routers where the prog.cgi program handling HNAP requests fails to validate user-supplied input before passing it to a system call, allowing authenticated attackers (or those bypassing auth) to execute arbitrary code with root privileges.

MitigationApply vendor firmware updates when available; until then, isolate affected devices on restricted network segments to limit exposure to network-adjacent attackers.

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 X3260 FirmwareOperating system
Affected:< 1.04b01

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
Adjacent
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:L/PR:L/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 device model
    Access the router web interface or check the device label; look for 'DIR-X3260' in the model designation
    Affected if The device is a D-Link DIR-X3260 router
  2. Check the installed firmware version
    Log into the router web interface, navigate to Status or Management section, and locate the firmware version field; alternatively, check via CLI if SSH/Telnet is enabled
    Affected if The firmware version is lower than 1.04b01 (e.g., 1.03, 1.02, etc.)
  3. Verify HNAP interface accessibility
    Attempt to access the prog.cgi endpoint via HTTP/HTTPS (commonly at /HNAP1/ or via the cgi-bin/prog.cgi URI); check if the router responds to HNAP SOAP requests
    Affected if The router exposes the HNAP interface and prog.cgi is reachable over the network
  4. Confirm authentication status
    Review whether default admin credentials remain in use, or test if the HNAP interface can be accessed without valid authentication (some configurations allow auth bypass)
    Affected if The device uses default credentials, has no strong password, or exhibits the documented authentication bypass behavior with HNAP requests

You are affected if you have a D-Link DIR-X3260 router running firmware below version 1.04b01 with the HNAP/prog.cgi interface exposed and accessible (with or without valid credentials).

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 1.04b01 or later
Fixed in 1.04b01
Interim mitigation

Apply vendor firmware updates when available; until then, isolate affected devices on restricted network segments to limit exposure to network-adjacent attackers.

Recommended fix High confidence

D-Link DIR-X3260 Firmware 1.04b01

  1. Identify the current firmware version of the D-Link DIR-X3260 router via the web management interface (typically at http://192.168.0.1 or http://192.168.1.1)
  2. Navigate to the firmware update or administration section of the router's web interface
  3. Download the firmware version 1.04b01 or later from the official D-Link support website (support.dlink.com)
  4. Upload and apply the firmware update through the router's web interface
  5. Wait for the router to complete the firmware upgrade process and reboot
  6. Verify the firmware version has been successfully updated to 1.04b01 or later
  7. Confirm the router is functioning normally and all settings are intact
Caveat Firmware updates may reset router configuration to defaults; back up configuration before upgrading if possible

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

Fix this in Dir X3260 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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