DrayTek Vigor2960: five web interface flaws fixed in firmware 1.5.1.7

Critical 9.9CVE-2026-129449 · CVE-2026-129450 · CVE-2026-129451 · CVE-2026-129452

DrayTek Vigor2960: five web interface flaws fixed in firmware 1.5.1.7

Five vulnerabilities published on 15 November 2026 affect the web management interface of the DrayTek Vigor2960 router. All five sit in the /cgi-bin/mainfunction.cgi handler. They are:

  • two command injection flaws
  • two path traversal flaws
  • one heap-based buffer overflow

All can be triggered remotely. Each needs an authenticated session on the device. Four are rated 9.9 and one 9.1 on the CVSS 3.1 scale.

According to the records, exploit details have been disclosed publicly for every one of these issues. However, none is listed in CISA’s Known Exploited Vulnerabilities (KEV) catalog. The records state that upgrading to firmware 1.5.1.7 addresses all five.

What’s affected

The issues affect DrayTek Vigor2960 firmware. Version 1.5.1.7 is listed as unaffected in every record.

  • CVE-2026-129449: command injection via the swmconfigupload argument (function sub_14914). Affected: 1.5.1.0 through 1.5.1.6.
  • CVE-2026-129450: path traversal via the option argument of the doWebBackup action. Affected: 1.5.1.6.
  • CVE-2026-129451: path traversal via the filename argument in app_guest_export. Affected: 1.5.1.0 through 1.5.1.6.
  • CVE-2026-129452: command injection via the jsondata argument in set_table. Affected: 1.5.1.6.
  • CVE-2026-129453: heap-based buffer overflow via the upload_name argument in check_file_exist, part of the File Existence Check component. Affected: 1.5.1.6.

Three of the records list only 1.5.1.6 as affected. That does not necessarily mean earlier releases are safe; they may simply not have been tested. Administrators on any release before 1.5.1.7 should treat their devices as exposed.

How serious is it

CVE-2026-129449, -129450, -129451 and -129453 are scored 9.9 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H. In plain terms:

  • the attack works over the network and is not complex;
  • it needs only a low-privileged account;
  • no user interaction is needed;
  • a successful attack can affect resources beyond the vulnerable component itself;
  • confidentiality, integrity and availability could all be fully compromised.

CVE-2026-129452 is scored 9.1 (Critical) with the vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H. It is the same, except that the attacker needs high (administrative) privileges.

Some of these scores come from the CVE Numbering Authority and some from NVD. All five NVD entries carry the status “Deferred”.

For an edge router, command injection and memory corruption are especially serious. A successful attack could give an attacker control of the device that sits between the internal network and the internet.

Is it being exploited?

As of the record date (17 November 2026), none of these CVEs is in CISA’s KEV catalog, and the records contain no reports of exploitation in the wild. However, each record states that the exploit has been disclosed publicly and may be used. Public research write-ups are linked in the references below. That lowers the bar for attackers, so the absence of a KEV listing should not delay patching.

What to do

  • Upgrade to firmware 1.5.1.7. The records name this as the fix for all five CVEs, and the firmware is available from DrayTek’s download server (linked below). After upgrading, check the running version.
  • Watch for further updates. The vendor’s statement in the records says the latest version “fixes many security issues”. It adds that “we have another one in our release plan which should solve the issues reported.” Check DrayTek for any newer release.
  • Restrict access to the management interface. Do not expose the web interface to the internet. Limit it to trusted management networks or addresses.
  • Review accounts. All five flaws require a logged-in user. Remove unneeded accounts, change default or weak passwords, and check for logins you don’t recognise.
  • Check for compromise on devices whose management interface was reachable from untrusted networks. Look for unexpected configuration changes or files.

References