cve.bz

CVE-2025-12295 dlink dap-2695 firmware

6.6 mediumExploit referenceEPSS 0.4%

Medium (6.6) in dlink dap-2695 firmware. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.

On this page
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.

Severity

CVSS 4.0

6.6 medium
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

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.4% (unchanged from 0.4% a week ago; 0.4% 30 days ago) estimated probability of exploitation activity in the next 30 days; 39th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2025-10-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-347 Improper Verification of Cryptographic Signature
CWE-345 Insufficient Verification of Data Authenticity
OWASP Top 10
A04:2025 Cryptographic Failures, A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2025-12295 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2025-12295?via=ask-ai-copy and https://cve.bz/cve/CVE-2025-12295?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2025-12295 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2025-12295

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2025-12295](https://cve.bz/cve/badge/CVE-2025-12295.svg)](https://cve.bz/cve/CVE-2025-12295)

HTML:

<a href="https://cve.bz/cve/CVE-2025-12295"><img src="https://cve.bz/cve/badge/CVE-2025-12295.svg" alt="CVE-2025-12295"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
dlink:dap-2695_firmware2.00:rc131

Attack patterns (CAPEC)

  • CAPEC-463 Padding Oracle Crypto Attack Severity: High
  • CAPEC-475 Signature Spoofing by Improper Validation Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-345 (12).

References

Check your stackJSON