D-Link DWR-M960 1.01.07 NTP Configuration Endpoint /boafrm/formNtp sub_4611CC submit-url stack-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 8.4 | $0-$5k | 1.33 |
Summary
A vulnerability was found in D-Link DWR-M960 1.01.07. It has been classified as critical. Affected is the function sub_4611CC of the file /boafrm/formNtp of the component NTP Configuration Endpoint. The manipulation of the argument submit-url leads to stack-based overflow.
This vulnerability is listed as CVE-2026-2854. The attack may be initiated remotely. In addition, an exploit is available.
Details
A vulnerability was found in D-Link DWR-M960 1.01.07. It has been rated as critical. This issue affects the function sub_4611CC of the file /boafrm/formNtp of the component NTP Configuration Endpoint. The manipulation of the argument submit-url 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-2026-2854. 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 02/23/2026).
The exploit is available at github.com. It is declared as proof-of-concept.
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 CERT Bund (WID-SEC-2026-0476). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Affected
- D-LINK Router
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.8VulDB Meta Temp Score: 8.4
VulDB Base Score: 8.8
VulDB Temp Score: 8.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: 🔒
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
02/20/2026 Advisory disclosed02/20/2026 VulDB entry created
02/23/2026 VulDB entry last update
Sources
Vendor: dlink.comAdvisory: github.com
Status: Not defined
CVE: CVE-2026-2854 (🔒)
GCVE (CVE): GCVE-0-2026-2854
GCVE (VulDB): GCVE-100-347093
CERT Bund: WID-SEC-2026-0476 - D-LINK DWR-M960 Router: Mehrere Schwachstellen ermöglichen Codeausführung und DoS
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/20/2026 11:43 AMUpdated: 02/23/2026 12:04 PM
Changes: 02/20/2026 11:43 AM (57), 02/22/2026 08:12 PM (31), 02/23/2026 12:04 PM (7)
Complete: 🔍
Submitter: LX-66-LX
Cache ID: 244:712:40
Submit
Accepted
- Submit #754457: D-Link DWR-M960 V1.0.07 Stack-based Buffer Overflow (by LX-66-LX)
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.