dbcve.org
Dap 1325 FirmwareOperating system · Dlink

CVE-2023-41191

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 Mode 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-18811.

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

Command injection vulnerability in D-Link DAP-1325 routers where the HNAP1 SOAP endpoint's SetAPLanSettings function fails to validate user-supplied input before passing it to a system call. Attackers can inject arbitrary commands without authentication and achieve root-level code execution.

MitigationApply available firmware update from D-Link; if no patch exists due to EOL status, isolate the device on a restricted network segment and consider replacement.

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. Identify the device model
    Access the router's web interface (typically at http://192.168.0.1 or http://192.168.1.1) and check the device information page, or check the device label for the model number DAP-1325
    Affected if The device is not a D-Link DAP-1325 router, then this CVE does not apply
  2. Determine the firmware version
    In the router's web interface, navigate to Status or System Settings page to view the firmware version. The version is typically displayed as a build number such as 1.09 or 1.08
    Affected if The firmware version is 1.09b03 or higher (including any version >= 1.09b03), then the device is NOT vulnerable. Versions below 1.09b03 are affected
  3. Verify HNAP1 SOAP endpoint accessibility
    Attempt to access the HNAP1 endpoint by sending an HTTP GET request to http://<router-ip>/HNAP1/ or http://<router-ip>/soap/HNAP1/
    Affected if The HNAP1 endpoint is not reachable from the network (blocked by firewall or disabled), the exploitation vector is limited but the device firmware version still determines vulnerability status
  4. Check for the SetAPLanSettings function
    Send an HTTP POST request to the HNAP1 endpoint with a SOAP envelope containing the SetAPLanSettings action to observe if the function accepts unauthenticated requests
    Affected if The SetAPLanSettings function responds to unauthenticated requests and appears to process parameters without authentication, the device is exploitable if firmware version is below 1.09b03

The device is affected if it is a D-Link DAP-1325 router running firmware version lower than 1.09b03 and the HNAP1 SOAP endpoint is 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.09b03 or later
Fixed in 1.09b03
Interim mitigation

Apply available firmware update from D-Link; if no patch exists due to EOL status, isolate the device on a restricted network segment and consider replacement.

Recommended fix High confidence

D-Link DAP-1325 Firmware version 1.09b03 or later

  1. 1. Download the latest firmware version 1.09b03 or later from the official D-Link support website.
  2. 2. Access the DAP-1325 router web management interface.
  3. 3. Navigate to the Administration or System Settings section.
  4. 4. Locate the firmware upgrade option.
  5. 5. Upload the downloaded firmware file and initiate the upgrade.
  6. 6. Wait for the upgrade to complete and the device to reboot.
  7. 7. Verify the firmware version in the router's admin panel to confirm the update was successful.

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

Fix this in Dap 1325 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,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 $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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