D-Link DI-8100 16.07.26A1 Web Management Interface /url_member.asp Name buffer overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.5 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in D-Link DI-8100 16.07.26A1 and classified as critical. This vulnerability affects unknown code of the file /url_member.asp of the component Web Management Interface. The manipulation of the argument Name leads to buffer overflow. This vulnerability is listed as CVE-2026-7856. The attack may be initiated remotely. In addition, an exploit is available.
Details
A vulnerability was found in D-Link DI-8100 16.07.26A1. It has been rated as critical. This issue affects an unknown part of the file /url_member.asp of the component Web Management Interface. The manipulation of the argument name with an unknown input leads to a buffer overflow vulnerability. Using CWE to declare the problem leads to CWE-120. The product copies an input buffer to an output buffer without verifying that the size of the input buffer is less than the size of the output buffer, leading to a buffer overflow. Impacted is confidentiality, integrity, and availability.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-7856. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are necessary for exploitation. 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 05/06/2026).
The exploit is available at github.com. It is declared as proof-of-concept. By approaching the search of inurl:url_member.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-2026-27486). 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: 🔍
CVSSv3
VulDB Meta Base Score: 7.2VulDB Meta Temp Score: 6.5
VulDB Base Score: 7.2
VulDB Temp Score: 6.5
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Buffer overflowCWE: CWE-120 / 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
05/05/2026 Advisory disclosed05/05/2026 VulDB entry created
05/06/2026 VulDB entry last update
Sources
Vendor: dlink.comAdvisory: github.com
Status: Not defined
CVE: CVE-2026-7856 (🔒)
GCVE (CVE): GCVE-0-2026-7856
GCVE (VulDB): GCVE-100-361133
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 05/05/2026 13:46Updated: 05/06/2026 01:21
Changes: 05/05/2026 13:46 (56), 05/06/2026 01:21 (1)
Complete: 🔍
Submitter: draw
Cache ID: 216::103
Submit
Accepted
- Submit #807849: D-Link DI-8100 16.07.26A1 Denial of Service (by draw)
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.