dbcve.org
Dir X3260 FirmwareOperating system · Dlink

CVE-2023-51614

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 SetQuickVPNSettings Password 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-21591.

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 stack-based buffer overflow exists in the prog.cgi binary of D-Link DIR-X3260 routers. The SetQuickVPNSettings function copies a user-supplied string to a fixed-length stack buffer without proper length validation, allowing authenticated network-adjacent attackers to execute arbitrary code in root context.

MitigationApply available firmware updates from D-Link; if unavailable, disable remote management interfaces and restrict network access to trusted users 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 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 router model
    Check the device label or web interface for the exact model number to confirm it is a D-Link DIR-X3260
    Affected if The device is a D-Link DIR-X3260 router
  2. Check the installed firmware version
    Access the router web interface (typically at 192.168.0.1) and navigate to the Administration or Status section to view the firmware version, or check via CLI if available
    Affected if The firmware version is less than 1.04b01
  3. Determine if remote management is enabled
    Check the router web interface under Administration > Remote Management to see if HTTP/HTTPS management from WAN is permitted
    Affected if Remote management interfaces are exposed to untrusted networks
  4. Check if the prog.cgi endpoint is accessible
    Attempt to access http://[router-ip]/prog.cgi or check if the CGI interface is reachable from the network
    Affected if The prog.cgi binary is accessible over the network
  5. Verify if QuickVPN settings are configurable
    Look for QuickVPN or VPN-related settings in the router web interface under VPN or Network settings
    Affected if QuickVPN functionality is enabled and exposed

You are affected if you have a D-Link DIR-X3260 router running firmware version lower than 1.04b01 with remote management or the prog.cgi interface accessible on the network.

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, disable remote management interfaces and restrict network access to trusted users only.

Recommended fix High confidence

D-Link DIR-X3260 Firmware version 1.04b01

  1. Identify the current firmware version of the D-Link DIR-X3260 router by accessing the web management interface or checking via SNMP
  2. Download the firmware version 1.04b01 or later from the official D-Link support website (supportannouncement.us.dlink.com)
  3. Backup the current router configuration before performing the upgrade
  4. Access the router's administration panel and navigate to the firmware upgrade section
  5. Upload the downloaded firmware file and initiate the upgrade process
  6. Wait for the router to complete the firmware update and reboot automatically
  7. Verify the new firmware version is 1.04b01 or higher after the reboot
  8. Confirm the router is functioning normally and all VPN/QuickVPN settings are intact

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
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,240
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,384.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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