CVE-2026-2218VulnerabilityPublished 9 Feb 2026Updated 23 Feb 2026

CVE-2026-2218: D-Link DCS-933L · Command Injection

Affects D-Link DCS-933LSource CVE Database V5

Not known to be exploited · CVSS 5.3 Medium · end of life, no fix coming : replace or isolate D-Link DCS-933L; no fix will be released.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 4.4% chance of exploitation in 30 days – higher than 91% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: None coming – the product is end of life

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

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 9 Feb 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

No fix will be released: D-Link DCS-933L is end of life. Replace it, or isolate it from untrusted networks until you can.

Affected software

Product	Affected	Fixed in
D-LinkDCS-933L	Affected =1.14.0 =1.14.1 =1.14.2 =1.14.3 =1.14.4 =1.14.5 =1.14.6 =1.14.7 =1.14.8 =1.14.9 =1.14.10 =1.14.11	Fixed in–

AI-suggested

1. Immediately isolate affected D-Link DCS-933L devices from untrusted networks, especially the internet, to prevent remote exploitation. 2. Implement strict network segmentation and firewall rules to restrict access to the camera management interfaces only to trusted administrators. 3. Replace legacy DCS-933L devices with newer, supported models that receive security updates and patches. 4. If replacement is not immediately feasible, disable or restrict access to the /setSystemAdmin endpoint if possible via device configuration or network controls. 5. Monitor network traffic for unusual commands or access attempts targeting the cameras. 6. Employ intrusion detection/prevention systems (IDS/IPS) tuned to detect command injection patterns or suspicious activity related to these devices. 7. Conduct regular security audits to identify any legacy devices still in operation and assess their exposure. 8. Educate administrators about the risks of unsupported devices and the importance of timely hardware refresh cycles.

Description

A vulnerability was determined in D-Link DCS-933L up to 1.14.11. This affects an unknown function of the file /setSystemAdmin of the component alphapd. This manipulation of the argument AdminID causes command injection. Remote exploitation of the attack is possible. The exploit has been publicly disclosed and may be utilized. This vulnerability only affects products that are no longer supported by the maintainer.

Impact

The primary impact of CVE-2026-2218 is unauthorized remote command execution on affected D-Link DCS-933L devices. This can lead to compromise of the device’s confidentiality, integrity, and availability. Attackers could potentially manipulate camera settings, intercept or alter video streams, or use the device as a foothold for lateral movement within a network. Since these cameras are often deployed in home, small business, or enterprise environments for security monitoring, exploitation could result in privacy violations, loss of surveillance data, or disruption of security operations. The lack of vendor support and patches increases the risk as organizations cannot remediate via updates, forcing reliance on compensating controls. Given the medium CVSS score and the public disclosure of the exploit, there is a moderate risk of targeted attacks, especially in environments where these devices remain in use without adequate network protections.

Summary

CVE-2026-2218 is a medium-severity command injection vulnerability affecting the D-Link DCS-933L IP camera firmware versions 1.14.0 through 1.14.11. The vulnerability resides in the /setSystemAdmin endpoint within the alphapd component, where the AdminID parameter is improperly sanitized, allowing an attacker to inject and execute arbitrary system commands remotely. The flaw requires low privileges (PR:L) but no user interaction (UI:N) and can be exploited over the network (AV:N). The vulnerability impacts confidentiality, integrity, and availability to a limited extent (VC:L, VI:L, VA:L). The affected devices are legacy and no longer supported by D-Link, meaning no official patches or updates are available. The exploit has been publicly disclosed, increasing the likelihood of exploitation attempts, although no active exploits in the wild have been reported. Due to the nature of IP cameras often being connected to sensitive networks or used for surveillance, successful exploitation could lead to unauthorized access, data leakage, or disruption of monitoring capabilities.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 23 Feb 2026, 21:10 UTC

Technical details

References

Community reviews

Related threats