dbcve.org
Dir X3260 FirmwareOperating system · Dlink

CVE-2023-51613

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 prog.cgi SetDynamicDNSSettings Stack-Based Buffer Overflow Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of D-Link DIR-X3260 routers. Authentication is required to exploit this vulnerability. The specific flaw exists within the prog.cgi binary, 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 copying it to a fixed-length stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-21590.

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

Stack-based buffer overflow in prog.cgi binary on D-Link DIR-X3260 routers. The vulnerability exists due to lack of proper validation of user-supplied string length before copying to a fixed-length stack buffer when handling HNAP requests. An authenticated attacker can exploit this to execute arbitrary code with root privileges.

MitigationApply available firmware updates from D-Link; if unavailable, restrict access to the router's web interface (ports 80/443) to trusted networks only or disable remote management.

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. Confirm router model is DIR-X3260
    Log into the router web interface or check the device label/menu to verify the exact model number.
    Affected if Model is D-Link DIR-X3260 and firmware is below version 1.04b01
  2. Check installed firmware version
    Access router web interface, look under Administration, System, or Settings for firmware version information. Compare against 1.04b01.
    Affected if Firmware version is lower than 1.04b01 (e.g., 1.04b00, 1.03, etc.)
  3. Verify web interface is accessible
    Attempt to reach the router at its LAN IP or WAN IP on ports 80 (HTTP) or 443 (HTTPS).
    Affected if Web interface responds on any network interface (LAN or WAN)
  4. Check if remote management is enabled
    In router web interface, look under Administration, Management, or Remote Access settings for remote management toggle.
    Affected if Remote management is enabled and web interface is accessible from WAN
  5. Confirm HNAP service availability
    Send an HTTP request to the router with a SOAPAction header pointing to HNAP (e.g., /HNAP1/). Check if the device responds to HNAP requests.
    Affected if Router responds to HNAP requests (indicates HNAP is enabled)

If the device is a D-Link DIR-X3260 running firmware below 1.04b01 and has its web interface accessible (especially remotely), it is likely affected by this 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 1.04b01 or later
Fixed in 1.04b01
Interim mitigation

Apply available firmware updates from D-Link; if unavailable, restrict access to the router's web interface (ports 80/443) to trusted networks only or disable remote management.

Recommended fix High confidence

D-Link DIR-X3260 Firmware version 1.04b01 or later

  1. 1. Download the fixed firmware version 1.04b01 (or later) from D-Link's official support website for the DIR-X3260 router
  2. 2. Access the router's web management interface via HTTP (port 80) or HTTPS (port 443)
  3. 3. Navigate to the Administration or System Settings section of the web interface
  4. 4. Locate the firmware upgrade option
  5. 5. Upload the downloaded fixed firmware file and apply the update
  6. 6. Wait for the firmware upload and installation to complete
  7. 7. Restart or reboot the router as prompted to ensure the new firmware is fully applied
  8. 8. After reboot, verify the firmware version in the router's web interface to confirm the update was successful
Caveat Firmware updates may reset router configuration to defaults; backup current settings before upgrading if needed

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

Fix this in Dir X3260 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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