dbcve.org
Dap 2695 FirmwareOperating system · Dlink

CVE-2025-12296

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-27
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
Public exploit 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 security vulnerability has been detected in D-Link DAP-2695 2.00RC13. The impacted element is the function sub_4174B0 of the component Firmware Update Handler. The manipulation leads to os command injection. The attack may be initiated remotely. The exploit has been disclosed publicly 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

A critical OS command injection vulnerability exists in the Firmware Update Handler (function sub_4174B0) of D-Link DAP-2695 access points running firmware 2.00RC13. The flaw allows remote, unauthenticated attackers to execute arbitrary operating system commands on the affected device due to insufficient input validation in the firmware update functionality.

MitigationThis device is end-of-life and no longer supported by D-Link; there is no vendor patch available. Organizations should immediately isolate the device on a restricted network segment, disable any exposed management interfaces, and replace with a supported alternative.

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 2695 FirmwareOperating system
Affected:= 2.00

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 management interface or check the physical device label to confirm the model is D-Link DAP-2695
    Affected if Device model is D-Link DAP-2695
  2. Check firmware version
    Log into the device web interface and navigate to the Status or System Information page to view the installed firmware version
    Affected if Firmware version is 2.00 (specifically 2.00RC13)
  3. Verify firmware update handler is accessible
    Check if the firmware update functionality is exposed via the web management interface or any API endpoint
    Affected if Firmware update interface is accessible without additional authentication barriers beyond default login
  4. Confirm remote management is enabled
    Inspect the device network settings to determine if remote (WAN) web management or the firmware update handler is exposed to external networks
    Affected if Remote management is enabled and the device is accessible from untrusted networks

You are affected if you have a D-Link DAP-2695 device running firmware version 2.00 with the firmware update interface accessible either locally or remotely.

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

This device is end-of-life and no longer supported by D-Link; there is no vendor patch available. Organizations should immediately isolate the device on a restricted network segment, disable any exposed management interfaces, and replace with a supported alternative.

Recommended fix High confidence
  1. Immediately isolate the affected device on a restricted network segment to limit remote attack surface
  2. Disable or block external access to the device's management interface via firewall rules
  3. If firmware update functionality is not required, disable or restrict it
  4. Monitor network traffic for suspicious patterns targeting this device
  5. Consider replacing the EOL device with a currently supported alternative from a vendor that provides security updates
  6. Implement intrusion detection/prevention systems to detect potential exploitation attempts

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

Fix this in Dap 2695 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Review / QA2.0 h
6.0 hours of engineering $1,160
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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