dbcve.org
Dap 1320 FirmwareOperating system · Dlink

CVE-2025-1539

CRITICAL · 9.8 CVSS v3.1 Published 2025-02-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable 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
A vulnerability, which was classified as critical, has been found in D-Link DAP-1320 1.00. Affected by this issue is the function replace_special_char of the file /storagein.pd-XXXXXX. The manipulation leads to stack-based buffer overflow. The attack may be launched remotely. The exploit has been disclosed to the public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

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

Stack-based buffer overflow in the replace_special_char function within the /storagein.pd-XXXXXX file allows remote attackers to overflow a stack-allocated buffer via specially crafted input, potentially enabling arbitrary code execution. The CVSS 9.8 indicates trivial exploitability with no authentication required.

MitigationReplace unsupported D-Link DAP-1320 devices with currently supported hardware, as no firmware patch will be released. If replacement is not immediately feasible, isolate the device behind a firewall and disable remote management to reduce attack surface.

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 1320 FirmwareOperating system
Affected:= 1.0

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

CVSS:3.1/AV:N/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 device model
    Access the device admin interface or check the physical device label to confirm the model is D-Link DAP-1320
    Affected if Device is not a D-Link DAP-1320 unit
  2. Check firmware version
    Log into the D-Link DAP-1320 web interface and navigate to Status or Management section to view the installed firmware version, or use SNMP/CLI commands if available
    Affected if Firmware version is 1.0
  3. Verify vulnerable component exists
    Attempt to access the device via SSH or Telnet (if enabled) and check for the presence of /storagein.pd* files in the filesystem, or use web interface to inspect if the storage input functionality is present
    Affected if The /storagein.pd-XXXXXX file with replace_special_char function exists on the device
  4. Check remote management exposure
    Verify if remote management/admin interface is accessible from WAN (internet-facing) by checking port forwarding rules, firewall settings, or the device's remote management configuration in the admin panel
    Affected if Remote management or the specific vulnerable feature is exposed to untrusted networks without authentication barriers

You are affected if you have a D-Link DAP-1320 device running firmware version 1.0 with the vulnerable /storagein.pd-XXXXXX component exposed to network attackers.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace unsupported D-Link DAP-1320 devices with currently supported hardware, as no firmware patch will be released. If replacement is not immediately feasible, isolate the device behind a firewall and disable remote management to reduce attack surface.

Recommended fix High confidence
  1. This vulnerability affects D-Link DAP-1320 firmware version 1.00, which is explicitly stated as a product that is no longer supported by the maintainer.
  2. No patch or firmware update is available from D-Link for this end-of-life device.
  3. Consider replacing the affected DAP-1320 device with a currently supported model from D-Link or another vendor.
  4. If replacement is not immediately possible, isolate the device on a restricted network segment to minimize exposure to remote attacks.
Caveat The DAP-1320 firmware 1.00 is end-of-life with no vendor support or updates available

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

Fix this in Dap 1320 Firmware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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