Skip to main content
VulnerabilityPublished

CVE-2026-129449: DrayTek Vigor2960 · Command Injection

Affects DrayTek Vigor2960Source CVE Database V5

0
Compare

Public exploit available · CVSS 9.4 Critical · fixed in 1.5.1.7 : patch DrayTek Vigor2960 as a priority.

Data as of 15 Nov 2026, 11:23 UTC

CVSS 4.0 base score
9.4Critical
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (VulDB)CVSS 4.09.4
CNA (VulDB)CVSS 3.19.9
CNA (VulDB)CVSS 3.09.9
CNA (VulDB)CVSS 2.09.0
Patch
Available – fixed in 1.5.1.7
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 15 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    CVSS exploit maturity: proof of concept public

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 14 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
DrayTekVigor2960Affected
  • 1.5.1.0 – 1.5.1.6
7 affected builds
Fixed in–

AI-suggested

Upgrade affected DrayTek Vigor2960 devices to firmware version 1.5.1.7 or later, as this version fixes the command injection vulnerability. The vendor recommends applying this update promptly to mitigate the risk. No additional mitigations are specified by the vendor.

Description

CVE-2026-129449 is a critical command injection vulnerability in DrayTek Vigor2960 firmware versions 1.5.1.0 through 1.5.1.6. The flaw exists in the sub_14914 function of /cgi-bin/mainfunction.cgi, where manipulation of the swmconfigupload argument allows remote attackers to execute arbitrary commands. Public exploit details have been disclosed. Upgrading to version 1.5.1.7 resolves this issue.

References

Community reviews

Loading reviews…