dbcve.org
Dap 2695 FirmwareOperating system · Dlink

CVE-2025-11665

CRITICAL · 9.8 CVSS v3.1 Published 2025-10-13
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 vulnerability was detected in D-Link DAP-2695 2.00RC131. This affects the function fwupdater_main of the file rgbin of the component Firmware Update Handler. Performing manipulation results in os command injection. The attack may be initiated remotely. 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 · moderate confidence

OS command injection vulnerability in the firmware update handler (fwupdater_main function in rgbin) of D-Link DAP-2695 firmware 2.00RC131 allows remote attackers to execute arbitrary operating system commands by manipulating the firmware update process.

MitigationSince the device is end-of-life and receives no further support, replace with a currently maintained device. If immediate replacement is not feasible, implement network segmentation, restrict management access to a dedicated VLAN, and apply strict firewall rules to block unauthorized management interface access.

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 the device model
    Log into the device web管理界面 or check the device label/marketing materials to confirm the model is D-Link DAP-2695
    Affected if The device is NOT a D-Link DAP-2695 (different models are not affected by this specific CVE)
  2. Check the installed firmware version
    Access the device web管理界面, navigate to System > Status or similar, and locate the firmware version field. Alternatively, check via CLI if available.
    Affected if The firmware version is exactly 2.00 (versions other than 2.00 are not affected)
  3. Verify the firmware update handler is accessible
    Check if the fwupdater_main function or firmware update feature is present on the device by attempting to access the firmware upgrade page in the web interface or checking for the rgbin binary via CLI if accessible
    Affected if The firmware update feature is enabled and accessible to an attacker (the command injection only applies when this feature can be manipulated)
  4. Assess network exposure of the management interface
    Review network configuration to determine if the device management interface (HTTP/HTTPS on ports 80/443 or similar) is exposed to untrusted networks or the internet
    Affected if The management interface is reachable from untrusted networks (remote attackers need network access to exploit the firmware update handler)

A user is affected if they have a D-Link DAP-2695 running firmware version 2.00 with the firmware update feature accessible from a network where untrusted attackers can reach the management interface.

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

Since the device is end-of-life and receives no further support, replace with a currently maintained device. If immediate replacement is not feasible, implement network segmentation, restrict management access to a dedicated VLAN, and apply strict firewall rules to block unauthorized management interface access.

Recommended fix High confidence
  1. This vulnerability affects D-Link DAP-2695 firmware version 2.00, which is explicitly stated as a product no longer supported by the maintainer.
  2. No vendor patch, firmware update, or upgrade path is available for this end-of-life product.
  3. Replace the affected D-Link DAP-2695 device with a currently supported model to mitigate this critical command injection vulnerability.
  4. If replacement is not immediately possible, network segmentation and restricting access to the device's management interface can reduce exposure, but these are workarounds only.
Caveat Device replacement required - no firmware fix available for this end-of-life product

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
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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