Skip to main content
Menu
CVEs

DrayTek Vigor2960 remote command execution in mainfunction.cgi

CVE-2026-129449EUVD-2026-126013GHSA-6VQP-3X8R-9QRRPublished November 15, 2026, updated

9.4CriticalCNA
Exploited
Proof of concept public, per CISA
Fix
Fix or patch referenced
Who is exposed
Not reported

Summary

DrayTek Vigor2960 has a command injection flaw in the sub_14914 function of its /cgi-bin/mainfunction.cgi file, where the swmconfigupload argument is not properly handled. An attacker can exploit it remotely over the network with low-level login access and inject commands to run on the device.

Written by a model

Original description

A security vulnerability has been detected in DrayTek Vigor2960 up to 1.5.1.6. Affected by this vulnerability is the function sub_14914 of the file /cgi-bin/mainfunction.cgi. The manipulation of the argument swmconfigupload leads to command injection. It is possible to initiate the attack remotely. The exploit has been disclosed publicly and may be used. Upgrading to version 1.5.1.7 addresses this issue. It is advisable to upgrade the affected component. The vendor recommends: "1.5.1.6 isn't the latest version of 2960, the latest version fixes many security issues. And we have another one in our release plan which should solve the issues reported."

What to do

Apply the patch listed under Evidence.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-129449 (DrayTek Vigor2960 mainfunction.cgi sub_14914 command injection), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-129449 (entry last updated 2026-11-16):
Affected:
- DrayTek Vigor2960: versions 1.5.1.0, 1.5.1.1, 1.5.1.2, 1.5.1.3, 1.5.1.4, 1.5.1.5, 1.5.1.6
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-129449 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-129449 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://fw.draytek.com.tw/Vigor2960/Firmware/v1.5.1.7/Vigor2960_v1.5.1.7.zip
- https://vuldb.com/vuln/437460
- https://vuldb.com/vuln/437460/cti
- https://vuldb.com/cve/CVE-2026-129449
- https://vuldb.com/submit/1044957
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-129449
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-129449"}.

Affected versions

cve.now Index

28of 100 · methodology v3
  • Exploitation15/40CISA rates a proof of concept as public
  • Exposure3/25Reachable over the network · Unknown: No advisory context yet
  • Reach?/20Unknown. No tracked technology or package matched
  • Severity10/10CVSS 9.4, total technical impact per CISA
  • No patch0/5No signal

What would change the score

  • Would score about 68 if added to CISA KEV
  • Would score about 63 if CISA's SSVC rates exploitation active
  • Would score about 47 if advisories confirm default setups are exposed

Timeline

  1. CVE published
  2. First seen by cve.now
  3. Posted on X by cve.now1 day
  4. CISA SSVC assessment

    Exploitation: poc · Automatable: no · Technical impact: total

  5. Record last updated

Public exploit activity

100%0Posted on X by cve.nowNov 15Nov 22
  • EPSS: 1.63%
  • Posted on X by cve.now Nov 15

Since disclosure: the repos PoC-in-GitHub lists and FIRST's daily EPSS score.

Evidence 8

KindSource
Vendor advisory 1Establishes: Affected and fixed versions.
Patchfw.draytek.com.tw · Vigor2960/Firmware/v1.5.1.7/Vigor2960_v1.5.1.7.zip
CVE record 2Establishes: The identifier and description.
RecordCVE List · CVE-2026-129449
RecordNVD · CVE-2026-129449
Public exploit code 1Establishes: Public exploit code exists (Exploit-DB, Metasploit, Nuclei and GitHub).
ExploitGitHub · yikesoftware/DrayTek_Vigor2960_Security_Analysis · cases/DRV2960-0015-authenticated-swmconfigupload-fieldname-command-injection
Other links 4
AdvisoryVulDB · Advisory #437460
AdvisoryVulDB · Threat intelligence #437460
AdvisoryVulDB · CVE-2026-129449 record
AdvisoryVulDB · Submission #1044957

Questions about CVE-2026-129449

Is CVE-2026-129449 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.

Source: cve.now feed data

Which versions are affected by CVE-2026-129449?

Vigor2960: versions 1.5.1.0, 1.5.1.1, 1.5.1.2, 1.5.1.3, 1.5.1.4 and 2 more.

Source: cve.now feed data

No corrections so far. Something wrong on this page? Report an error.