# CVE-2025-12295: D-Link DAP-2695 Firmware Update sub_40C6B8 signature verification

> Remote attackers can bypass firmware signature verification to install malicious code on unsupported D-Link access points.

- **Severity:** High 7.5 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Oct 2025
- **Updated:** 27 Oct 2025
- **Also known as:** GHSA-fmw9-c6hw-79vg

## What is CVE-2025-12295?

CVE-2025-12295 is a high-severity vulnerability in D-Link DAP-2695, published on 27 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A weakness has been identified in D-Link DAP-2695 2.00RC13. The affected element is the function sub_40C6B8 of the component Firmware Update Handler. Executing manipulation can lead to improper verification of cryptographic signature. The attack can be launched remotely. Attacks of this nature are highly complex. The exploitability is described as difficult. The exploit has been made available to the public and could be exploited. This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-347 (Improper Verification of Cryptographic Signature), CWE-345 (Insufficient Verification of Data Authenticity)

## Which versions are affected by CVE-2025-12295?

It affects 1 product.


Products: Dlink Dap-2695 Firmware.

## How do I fix CVE-2025-12295?

No fix has been published for CVE-2025-12295 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-12295 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12295 exists.

## Other vulnerabilities in D-Link DAP-2695

- [CVE-2025-12296](https://insights.sbomify.com/CVE-2025-12296/): D-Link DAP-2695 Firmware Update sub_4174B0 os command injection (medium 5.1)
- [CVE-2025-11665](https://insights.sbomify.com/CVE-2025-11665/): D-Link DAP-2695 Firmware Update rgbin fwupdater_main os command injection (medium 5.1)
- [CVE-2025-4858](https://insights.sbomify.com/CVE-2025-4858/): D-Link DAP-2695 ARP Spoofing Prevention Page adv_arpspoofing.php cross site scripting (medium 4.8)
- [CVE-2025-4859](https://insights.sbomify.com/CVE-2025-4859/): D-Link DAP-2695 MAC Bypass Settings Page adv_macbypass.php cross site scripting (medium 4.8)
- [CVE-2025-4860](https://insights.sbomify.com/CVE-2025-4860/): D-Link DAP-2695 Static Pool Settings Page adv_dhcps.php cross site scripting (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12295 and fix it if it is affected.

What it is: CVE-2025-12295 is a high-severity vulnerability in D-Link DAP-2695, published on 27 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-12295 exists.

Affected product: D-Link DAP-2695. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12295/ (Markdown: https://insights.sbomify.com/CVE-2025-12295/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12295
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12295
- OSV: https://osv.dev/vulnerability/CVE-2025-12295

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12295/
Summaries are generated and may contain mistakes; the official description above is the record.