dbcve.org
Dap 1325 FirmwareOperating system · Dlink

CVE-2023-41188

HIGH · 8.8 CVSS v3.1 Published 2024-05-03
Fix available
A fix is available. Upgrade to 1.09b03 or later.
See remediation →
93/100
Remediation priority · Urgent
No privileges 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 DAP-1325 HNAP SetAPLanSettings DeviceName Command Injection Remote Code Execution Vulnerability. This vulnerability allows network-adjacent attackers to execute arbitrary code on affected installations of D-Link DAP-1325 routers. Authentication is not required to exploit this vulnerability. The specific flaw exists within the handling of a request parameter provided to the HNAP1 SOAP endpoint. 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-18808.

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 command injection vulnerability exists in the D-Link DAP-1325 router's HNAP1 SOAP endpoint. The SetAPLanSettings function does not validate the DeviceName parameter before using it in a system call, allowing an attacker to inject arbitrary commands. Since no authentication is required and the code executes as root, an attacker with network access can achieve full device compromise.

MitigationCheck for available firmware updates from D-Link; if unavailable, isolate the device behind a firewall, disable remote management interfaces, and consider replacing the end-of-life device.

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
Dap 1325 FirmwareOperating system
Affected:< 1.09b03

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

CVSS:3.1/AV:A/AC:L/PR:N/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. Verify firmware version
    Access the router web interface and navigate to Status or Management page to view the firmware version, or query the HNAP1 endpoint for the firmware information
    Affected if Firmware version is lower than 1.09b03
  2. Confirm HNAP1 SOAP endpoint is reachable
    Send an HTTP request to http://[router-ip]/HNAP1/ and verify the device responds to SOAP requests
    Affected if The HNAP1 endpoint is accessible from the network where the attacker resides
  3. Check remote management exposure
    Determine if the router's web interface (port 80/443) is exposed to WAN/internet or accessible from untrusted networks
    Affected if Remote management or the web interface is exposed beyond the local trusted network

The device is affected if the firmware version is below 1.09b03 AND the HNAP1 SOAP endpoint is reachable from the attacker's network location.

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.09b03 or later
Fixed in 1.09b03
Interim mitigation

Check for available firmware updates from D-Link; if unavailable, isolate the device behind a firewall, disable remote management interfaces, and consider replacing the end-of-life device.

Recommended fix High confidence

DAP-1325 Firmware 1.09b03 or later

  1. 1. Navigate to the official D-Link support page for the DAP-1325 device.
  2. 2. Locate the firmware download section for DAP-1325.
  3. 3. Download firmware version 1.09b03 or a later stable release.
  4. 4. Access the DAP-1325 router web management interface.
  5. 5. Navigate to the Administration or System Settings section.
  6. 6. Select the firmware upgrade option and upload the downloaded firmware file.
  7. 7. Wait for the upgrade process to complete and the device to reboot.
  8. 8. Verify the firmware version has been updated successfully.
Caveat Review D-Link release notes for the firmware to check for any configuration or feature changes that may affect your deployment

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

Fix this in Dap 1325 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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