CVE-2023-44422
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 · uneditedD-Link DIR-X3260 SetSysEmailSettings EmailFrom 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-21102.
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 confidenceCommand injection vulnerability in D-Link DIR-X3260 routers where the SetSysEmailSettings function in prog.cgi fails to validate user-supplied input from the EmailFrom parameter before passing it to a system call. This allows authenticated attackers (or those exploiting a separate auth bypass) to execute arbitrary commands as root via the lighttpd webserver on ports 80/443.
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< 1.04b01CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLocate the device label on the router or check the web interface status page for the model numberAffected if The device is not a D-Link DIR-X3260 (the vulnerability only affects this model)
-
Check the installed firmware versionAccess the router web interface (http://router IP) and navigate to the Administration or System settings section to view the firmware version; alternatively, check via CLI if telnet/ssh is enabledAffected if The firmware version is below 1.04b01 (versions prior to this are affected)
-
Verify if the web management interface is accessibleAttempt to access the router's IP address on ports 80 and 443 from the network segment you are checkingAffected if The lighttpd webserver on ports 80/443 is reachable from an untrusted network
-
Check remote management configurationIn the router web UI, navigate to Remote Management or Administration > Remote Management settingsAffected if Remote administration is enabled, allowing access to prog.cgi from outside the local network
You are affected if you have a D-Link DIR-X3260 router running firmware version below 1.04b01 with the web interface accessible (especially if remote management is enabled), since the vulnerability allows authenticated command injection via the EmailFrom parameter in SetSysEmailSettings.
Generated from the published advisory. Verify against your own configuration.
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 · scoped1.04b01
Apply vendor firmware patch when available; until then, restrict access to router management interface to trusted networks only and disable remote administration if not required.
D-Link DIR-X3260 Firmware version 1.04b01 or later
- 1. Obtain the latest firmware version for D-Link DIR-X3260 from the official D-Link support website (support.dlink.com).
- 2. Navigate to the router's web interface by accessing its IP address (typically 192.168.0.1 or 192.168.1.1) in a web browser.
- 3. Log into the router administration panel with administrator credentials.
- 4. Navigate to the firmware upgrade or system settings section (usually under 'Management' or 'System').
- 5. Upload and apply the firmware version 1.04b01 or later.
- 6. After the firmware update completes, verify the router reboots successfully and re-authenticate to confirm the update was applied.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2023-44422 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-44422 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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