CVE-2025-13188
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-11-14

Last updated on: 2025-11-20

Assigner: VulDB

Description
A vulnerability was detected in D-Link DIR-816L 2_06_b09_beta. Affected by this vulnerability is the function authenticationcgi_main of the file /authentication.cgi. Performing manipulation of the argument Password results in stack-based buffer overflow. Remote exploitation of the attack is possible. The exploit is now public and may be used. This vulnerability only affects products that are no longer supported by the maintainer.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-11-14
Last Modified
2025-11-20
Generated
2026-05-07
AI Q&A
2025-11-15
EPSS Evaluated
2026-05-05
NVD
Affected Vendors & Products
Showing 2 associated CPEs
Vendor Product Version / Range
dlink dir-816l_firmware 2.06.b09
dlink dir-816l *
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-119 The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary. This may result in read or write operations on unexpected memory locations that could be linked to other variables, data structures, or internal program data.
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).
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability is a stack-based buffer overflow in the authenticationcgi_main function of the /authentication.cgi file on the D-Link DIR-816L 2_06_b09_beta device. It occurs when the Password argument is manipulated, allowing an attacker to remotely exploit the device by overflowing the stack buffer.


How can this vulnerability impact me? :

The vulnerability allows remote attackers to execute arbitrary code or cause a denial of service by exploiting the stack-based buffer overflow. This can lead to full compromise of the affected device, potentially allowing unauthorized access and control.


What immediate steps should I take to mitigate this vulnerability?

Since the affected products are no longer supported by the maintainer and the exploit is public, immediate mitigation steps include isolating the vulnerable device from the network, disabling remote access to the /authentication.cgi interface if possible, and replacing the device with a supported and patched model to prevent exploitation.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart