dbcve.org
Dap 1325 FirmwareOperating system · Dlink

CVE-2023-41201

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 SetSetupWizardStatus Enabled 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-18821.

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 in D-Link DAP-1325 routers allows network-adjacent attackers to execute arbitrary code as root without authentication. The flaw exists in the HNAP1 SOAP endpoint's handling of a user-supplied parameter, which is passed to a system call without proper validation, enabling direct OS command execution.

MitigationApply the vendor-supplied firmware patch when available; until then, isolate affected devices on a restricted network segment to limit exposure to adjacent attackers.

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
    Locate the physical device or access its web admin interface and confirm the model number is D-Link DAP-1325
    Affected if Device is not a D-Link DAP-1325 unit (different models have different vulnerability status)
  2. Check the installed firmware version
    Access the router web interface (typically at 192.168.0.1 or 192.168.1.1), navigate to the Status or Management page, and locate the firmware version field
    Affected if Firmware version is lower than 1.09b03 (any version prior to this patch)
  3. Verify HNAP1 service is accessible
    Attempt to access the HNAP1 SOAP endpoint by sending an HTTP POST request to /HNAP1/ on the router's IP address
    Affected if The HNAP1 endpoint responds (the service is enabled and reachable on the network)
  4. Confirm the vulnerability is exploitable
    Send a crafted SOAP request to the HNAP1 endpoint with a test parameter that would trigger command execution if the flaw exists (note: only do this in authorized, owned environments)
    Affected if The device executes the injected command, confirming the command injection vulnerability is present

A user is affected if they own a D-Link DAP-1325 router running firmware version prior to 1.09b03 with the HNAP1 service exposed 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 the vendor-supplied firmware patch when available; until then, isolate affected devices on a restricted network segment to limit exposure to adjacent attackers.

Recommended fix Moderate confidence

DAP-1325 firmware version 1.09b03 or later

  1. 1. Identify the current firmware version of the DAP-1325 device via the web management interface
  2. 2. Navigate to the D-Link support page for the DAP-1325 at supportannouncement.us.dlink.com or official D-Link support channels
  3. 3. Download firmware version 1.09b03 or later from D-Link's official firmware repository
  4. 4. Access the router's web-based administration panel
  5. 5. Locate the firmware upgrade section (typically under Administration > Firmware Upgrade or System > Firmware)
  6. 6. Upload and apply the new firmware file
  7. 7. Allow the device to reboot and complete the update process
  8. 8. Verify the new firmware version is installed and the device is functioning normally
Caveat Firmware upgrades on routers may reset configuration to defaults; backup current settings before upgrading if possible

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

Fix this in Dap 1325 Firmware Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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