CVE-2026-71929 — DrayTek VigorSwitch Multiple Models OS Command Injection via setDevProto
Multiple DrayTek VigorSwitch models contain a command injection vulnerability in the setDevProto function. The vulnerability is caused by insufficient filtering of the username and password fields before command execution. A remote attacker can trigger this vulnerability via crafted input to execute arbitrary commands with root privileges. Exploitation requires valid administrative credentials for the device's web management interface.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- EPSS 2.3% (30-day exploitation probability)+12
- Technical severity (high)+6
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (DrayTek Corporation VigorSwitch FX2120, DrayTek Corporation VigorSwitch G1280, DrayTek Corporation VigorSwitch G1282…).
- No fix documented in the sources: reduce exposure and monitor the vendor advisory.
- Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| DrayTek Corporation | VigorSwitch FX2120 | < 3.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch G1280 | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch G1282 | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch G2100 | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch G2121 | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch G2280x | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch G2282x | < 2.10.6 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch G2540x | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch G2540xs | < 3.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch G2542x | < 3.10.6 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch P1280 | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch P1281x | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch P1282 | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch P2100 | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch P2121 | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch P2280x | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch P2282x | < 2.10.6 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch P2540x | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch P2540xs | < 3.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch P2542x | < 3.10.6 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch P2542xh | < 3.10.6 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch PQ2121x | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch PQ2200xb | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch PQ2300xb | < 2.10.7 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch PX2060 | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch Q2121x | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch Q2200x | < 2.9.10 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| DrayTek Corporation | VigorSwitch Q2300x | < 2.10.7 | Vulnerable | CVE Program (cve.org) e CISA ADP |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 8.6 | CVSS 4.0 | High | — | — | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 8.6 | CVSS 4.0 | High | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
| 7.2 | CVSS 3.1 | High | 1.2 | 5.9 | disclosure@vulncheck.com via NIST National Vulnerability Database |
| 7.2 | CVSS 3.1 | High | — | — | VulnCheck via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H (score shown at the top: disclosure@vulncheck.com) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
EPSS over time FIRST
Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 2.27%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Look for parameters with command/query metacharacters and unexpected child processes of the service.
Timeline
What happened to this CVE, newest first.
- 2026
- Affected products added · draytek corporation/vigorswitch g2540xs, draytek corporation/vigorswitch p2540xs, draytek corporation/vigorswitch fx2120
- SSVC assessment updated
- Record published
- CVSS changed · 7.2
- Source status changed · → Deferred
- Record created in this database
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
2 on the record
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-71943 DrayTek VigorSwitch Multiple Models OS Command Injection via setDevNet Aug 24, 2026
- High CVE-2026-71941 DrayTek VigorSwitch Multiple Models Buffer Overflow via diag_logmail Aug 24, 2026
- High CVE-2026-71938 DrayTek VigorSwitch Multiple Models Buffer Overflow via switch_lan_gvrp Aug 24, 2026
- High CVE-2026-71940 DrayTek VigorSwitch Multiple Models Buffer Overflow via acl_general_setup Edit ACE Aug 24, 2026
- High CVE-2026-71939 DrayTek VigorSwitch Multiple Models Buffer Overflow via acl_general_setup Add ACE Aug 24, 2026
- High CVE-2026-71942 DrayTek VigorSwitch Multiple Models Buffer Overflow via mail_mailalert Aug 24, 2026
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No fixed version, patch or mitigation documented.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2026-71929 is "DrayTek VigorSwitch Multiple Models OS Command Injection via setDevProto", rated High. It affects VigorSwitch FX2120 (DrayTek Corporation); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.2 describes technical severity. EPSS 2.27% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.