A vulnerability, which was classified as critical , has been found in D-Link DIR-513 1.10 . The impacted element is the function formEasySetTimezone of the file /goform/formEasySetTimezone of the component boa . This manipulation of the argument curTime causes stack-based buffer overflow. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is handled as CVE-2026-4555 . The attack can be initiated remotely. Additionally, an exploit exists.
Full text archived locally
✦ AI Summary· Claude Sonnet
VDB-352382 · CVE-2026-4555 · GCVE-100-352382
D-LINK DIR-513 1.10 BOA FORMEASYSETTIMEZONE CURTIME STACK-BASED OVERFLOW
HISTORYDIFFRELATEJSONXMLCTI
CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score
8.0 $0-$5k 3.09+
Summaryinfo
A vulnerability, which was classified as critical, was found in D-Link DIR-513 1.10. This affects the function formEasySetTimezone of the file /goform/formEasySetTimezone of the component boa. Such manipulation of the argument curTime leads to stack-based overflow. This vulnerability only affects products that are no longer supported by the maintainer. This vulnerability is uniquely identified as CVE-2026-4555. The attack can be launched remotely. Moreover, an exploit is present.
Detailsinfo
A vulnerability was found in D-Link DIR-513 1.10 and classified as critical. Affected by this issue is the function formEasySetTimezone of the file /goform/formEasySetTimezone of the component boa. The manipulation of the argument curTime 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 available at github.com. This vulnerability is handled as CVE-2026-4555. The exploitation is known to be easy. The attack may be launched remotely. Technical details as well as a public exploit are known. The structure of the vulnerability defines a possible price range of USD $0-$5k at the moment (estimation calculated on 03/21/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.
Productinfo
Type
Router Operating System
Vendor
D-Link
Name
DIR-513
Version
1.10
License
commercial
Support
end of life
Website
Vendor: https://www.dlink.com/
CPE 2.3info
🔒
CPE 2.2info
🔒
CVSSv4info
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv3info
VulDB Meta Base Score: 8.8
VulDB Meta Temp Score: 8.0
VulDB Base Score: 8.8
VulDB Temp Score: 8.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2info
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: 🔍
Exploitinginfo
Class: Stack-based overflow
CWE: CWE-121 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
0-Day Unlock Unlock Unlock Unlock
Today Unlock Unlock Unlock Unlock
Threat Intelligenceinfo
Interest: 🔍
Active Actors: 🔍
Active APT Groups: 🔍
Countermeasuresinfo
Recommended: no mitigation known
Status: 🔍
0-Day Time: 🔒
Timelineinfo
03/21/2026 Advisory disclosed
03/21/2026 +0 days VulDB entry created
03/21/2026 +0 days VulDB entry last update
Sourcesinfo
Vendor: dlink.com
Advisory: github.com
Status: Not defined
CVE: CVE-2026-4555 (🔒)
GCVE (CVE): GCVE-0-2026-4555
GCVE (VulDB): GCVE-100-352382
scip Labs: https://www.scip.ch/en/?labs.20161013
Entryinfo
Created: 03/21/2026 18:07
Changes: 03/21/2026 18:07 (59)
Complete: 🔍
Submitter: LtzHust2
Cache ID: 99:16C:101
Submitinfo
Accepted
Submit #774936: D-Link DIR-513 1.10 Stack-based Buffer Overflow (by LtzHust2)
Discussion
No comments yet. Languages: en.
Please log in to comment.
◂ PreviousOverviewNext ▸