cve.bz

CVE-2026-6014 dlink dir-513 firmware: Classic Buffer Overflow

7.4 highExploit referenceEPSS 0.7%

High (7.4) in dlink dir-513 firmware. EPSS 0.7% estimated probability of exploitation activity in the next 30 days.

On this page
A flaw has been found in D-Link DIR-513 1.10. This issue affects the function formAdvanceSetup of the file /goform/formAdvanceSetup of the component POST Request Handler. This manipulation of the argument webpage causes buffer overflow. It is possible to initiate the attack remotely. The exploit has been published and may be used. This vulnerability only affects products that are no longer supported by the maintainer.

Severity

CVSS 4.0

7.4 high
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:P

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
EPSS
0.7% (unchanged from 0.7% a week ago; 1.2% 30 days ago) estimated probability of exploitation activity in the next 30 days; 55th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-04-10. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-119 Improper Restriction of Operations within the Bounds of a Memory Buffer
CWE-120 Buffer Copy without Checking Size of Input (Classic Buffer Overflow)
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-6014 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-6014?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-6014?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-6014 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-6014

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-6014](https://cve.bz/cve/badge/CVE-2026-6014.svg)](https://cve.bz/cve/CVE-2026-6014)

HTML:

<a href="https://cve.bz/cve/CVE-2026-6014"><img src="https://cve.bz/cve/badge/CVE-2026-6014.svg" alt="CVE-2026-6014"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
dlink:dir-513_firmware1.10

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-119 (12), CWE-120 (13).

References

Check your stackJSON