CVE-2026-2260

D-Link Dcs-931l Firmware command injection

7.2 HIGHPublic exploitEPSS 5.80%

Published10 Feb 2026

Description

A vulnerability was found in D-Link DCS-931L up to 1.13.0. This affects an unknown part of the file /goform/setSysAdmin. The manipulation of the argument AdminID results in os command injection. The attack can be executed remotely. The exploit has been made public and could be used. This vulnerability only affects products that are no longer supported by the maintainer.

CVSS 3.1 breakdown

Attack vectorNetwork

Attack complexityLow

Privileges requiredHigh

User interactionNone

ScopeUnchanged

ConfidentialityHigh

IntegrityHigh

AvailabilityHigh

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Affected products

D-Link Dcs-931l Firmware≥ 1.0.0 ≤ 1.13.00

Remediation

No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.

References

https://github.com/cha0yang1/CVE/blob/main/DLinkRce.mdExploitThird Party Advisory
https://github.com/cha0yang1/CVE/blob/main/DLinkRce.md#pocExploitThird Party Advisory
https://vuldb.com/?ctiid.345007Permissions RequiredVDB Entry
https://vuldb.com/?id.345007Third Party AdvisoryVDB Entry
https://vuldb.com/?submit.753398Third Party AdvisoryVDB Entry
https://www.dlink.com/Product

Related CVEs

Recent high-severity vulnerabilities sharing a weakness type.

Frequently asked

Is CVE-2026-2260 being actively exploited?

CVE-2026-2260 is not in the CISA KEV catalog. A public exploit reference exists, so treat it as exploitable. Its EPSS exploit probability is 5.80%.

How severe is CVE-2026-2260?

CVE-2026-2260 has a CVSS 3.1 base score of 7.2, rated high. EPSS estimates a 5.80% probability of exploitation.

Which products are affected by CVE-2026-2260?

Affected products include D-Link Dcs-931l Firmware.

How do I fix CVE-2026-2260?

Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.

How Secuno handles this

Secuno correlates vulnerabilities like CVE-2026-2260 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.

See how prioritisation works Book a demo

Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.