cve.bz

CVE-2026-5311 dlink: Incorrect Privilege Assignment

5.5 mediumExploit referenceEPSS 1.0%

Medium (5.5) in dlink. EPSS 1.0% estimated probability of exploitation activity in the next 30 days.

On this page
A security flaw has been discovered in D-Link DNS-120, DNR-202L, DNS-315L, DNS-320, DNS-320L, DNS-320LW, DNS-321, DNR-322L, DNS-323, DNS-325, DNS-326, DNS-327L, DNR-326, DNS-340L, DNS-343, DNS-345, DNS-726-4, DNS-1100-4, DNS-1200-05 and DNS-1550-04 up to 20260205. Affected is the function Webdav_Access_List of the file /cgi-bin/file_center.cgi. Performing a manipulation of the argument cmd results in improper access controls. It is possible to initiate the attack remotely. The exploit has been released to the public and may be used for attacks.

Severity

CVSS 4.0

5.5 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P

CVSS 3.1

5.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
EPSS
1.0% (unchanged from 1.0% a week ago; 1.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 64th 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: yes · Technical impact: partial, assessed 2026-04-02. 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-266 Incorrect Privilege Assignment
CWE-284 Improper Access Control
OWASP Top 10
A01:2025 Broken Access Control, A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-5311 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-5311?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-5311?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-5311 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-5311

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-5311](https://cve.bz/cve/badge/CVE-2026-5311.svg)](https://cve.bz/cve/CVE-2026-5311)

HTML:

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

Affected

Versions

From the NVD's CPE matches.

ProductAffected
dlink:dnr-202l_firmwarethrough 2026-02-05
dlink:dnr-326_firmwarethrough 2026-02-05
dlink:dns-1100-4_firmwarethrough 2026-02-05
dlink:dns-120_firmwarethrough 2026-02-05
dlink:dns-1200-05_firmwarethrough 2026-02-05
dlink:dns-1550-04_firmwarethrough 2026-02-05
dlink:dns-315l_firmwarethrough 2026-02-05
dlink:dns-320_firmwarethrough 2026-02-05
dlink:dns-320l_firmwarethrough 2026-02-05
dlink:dns-320lw_firmwarethrough 2026-02-05
dlink:dns-321_firmwarethrough 2026-02-05
dlink:dns-322l_firmwarethrough 2026-02-05
dlink:dns-323_firmwarethrough 2026-02-05
dlink:dns-325_firmwarethrough 2026-02-05
dlink:dns-326_firmwarethrough 2026-02-05
dlink:dns-327l_firmwarethrough 2026-02-05
dlink:dns-340l_firmwarethrough 2026-02-05
dlink:dns-343_firmwarethrough 2026-02-05
dlink:dns-345_firmwarethrough 2026-02-05
dlink:dns-726-4_firmwarethrough 2026-02-05

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-284 (17).

References

Check your stackJSON