D-Link DI-8100 16.07.26A1 HTTP Request /menu_nat_more.asp stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in D-Link DI-8100 16.07.26A1. It has been rated as critical. Affected by this issue is some unknown functionality of the file /menu_nat_more.asp of the component HTTP Request Handler. The manipulation leads to stack-based overflow. This vulnerability is uniquely identified as CVE-2025-7762. The attack is possible to be carried out remotely. Moreover, an exploit is present.
Details
A vulnerability, which was classified as critical, has been found in D-Link DI-8100 16.07.26A1. This issue affects an unknown function of the file /menu_nat_more.asp of the component HTTP Request Handler. The manipulation with an unknown input leads to a stack-based overflow vulnerability. Using CWE to declare the problem leads to CWE-121. A stack-based buffer overflow condition is a condition where the buffer being overwritten is allocated on the stack (i.e., is a local variable or, rarely, a parameter to a function). Impacted is confidentiality, integrity, and availability.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2025-7762. The exploitation is known to be easy. The attack may be initiated remotely. Technical details as well as a public exploit are known. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 07/24/2025).
The exploit is available at github.com. It is declared as proof-of-concept. By approaching the search of inurl:menu_nat_more.asp it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2025-21829). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
Website
- Vendor: https://www.dlink.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 8.0VulDB Meta Temp Score: 7.8
VulDB Base Score: 8.8
VulDB Temp Score: 8.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔒
CNA Base Score: 8.8
CNA Vector: 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Stack-based overflowCWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Google Hack: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
07/17/2025 Advisory disclosed07/17/2025 VulDB entry created
07/24/2025 VulDB entry last update
Sources
Vendor: dlink.comAdvisory: github.com
Status: Not defined
CVE: CVE-2025-7762 (🔒)
GCVE (CVE): GCVE-0-2025-7762
GCVE (VulDB): GCVE-100-316757
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 07/17/2025 16:29Updated: 07/24/2025 03:18
Changes: 07/17/2025 16:29 (55), 07/18/2025 01:14 (1), 07/22/2025 15:25 (32), 07/24/2025 03:18 (11)
Complete: 🔍
Submitter: XiDP
Cache ID: 216::103
Submit
Accepted
- Submit #615796: D-Link DI-8100 16.07.26A1 Buffer Overflow (by XiDP)
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.