dbcve.org
Dir X3260 FirmwareOperating system · Dlink

CVE-2023-51621

MEDIUM · 6.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.04b01 or later.
See remediation →
70/100
Remediation priority · Elevated
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 SetDeviceSettings 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-size stack-based buffer. An attacker can leverage this vulnerability to execute code in the context of root. Was ZDI-CAN-21670.

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 D-Link DIR-X3260 routers prog.cgi binary. The vulnerability exists in HNAP request handling where user-supplied input is copied to a fixed-size stack buffer without bounds checking, allowing authenticated attackers to execute arbitrary code as root.

MitigationApply vendor firmware patch when available; until then, restrict administrative access to trusted users only and disable remote management if possible.

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

CVSS:3.1/AV:A/AC:L/PR:H/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/marketing materials to confirm the exact model is D-Link DIR-X3260
    Affected if The device is not a DIR-X3260 model
  2. Check the installed firmware version
    Log into the router web interface and navigate to Status or Management section to view the firmware version; alternatively, use the command 'cat /proc/version' or 'grep VERSION /etc/os-release' via telnet/SSH if available
    Affected if The firmware version is any version prior to 1.04b01 (e.g., 1.04b00, 1.03, etc.)
  3. Verify if the HNAP interface is accessible
    Attempt to access the prog.cgi endpoint via HTTP/HTTPS (typically at /HNAP1/ or via the main CGI endpoint); send a request to the router's IP on ports 80 or 443
    Affected if The HNAP interface responds to requests, indicating the prog.cgi binary with the vulnerability is in use
  4. Check remote management settings
    In the router web interface, navigate to Advanced > Remote Management or similar; verify if Remote Management is enabled and which IP addresses or ranges are permitted
    Affected if Remote management is enabled and accessible from untrusted networks (e.g., WAN)

You are affected if you have a DIR-X3260 router running firmware version below 1.04b01 with the HNAP interface exposed to untrusted users.

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 patch when available; until then, restrict administrative access to trusted users only and disable remote management if possible.

Recommended fix High confidence

Firmware version 1.04b01 or later

  1. Obtain firmware version 1.04b01 or later from D-Link's official support website (supportannouncement.us.dlink.com)
  2. Access the D-Link DIR-X3260 router's web management interface via HTTP or HTTPS
  3. Log in with administrator credentials
  4. Navigate to the System or Administration section of the router settings
  5. Locate the Firmware Upgrade or Update option
  6. Upload the fixed firmware file (1.04b01 or later)
  7. Wait for the firmware upload and installation to complete - do not power off the device
  8. After reboot, verify the firmware version has been updated
Caveat Router firmware upgrades may reset configuration to defaults; back up current settings 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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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