On this page (7 sections)
A command injection vulnerability, tracked as CVE-2026-129449, has been reported in DrayTek Vigor2960 firmware. According to the GitHub Advisory Database entry, firmware up to 1.5.1.6 is affected, the issue can be triggered remotely, and the advisory states the exploit has been disclosed publicly.
If you manage a Vigor2960 at an office, a branch or a client site, confirm its firmware version and plan an upgrade to 1.5.1.7. Coverage so far is thin: the advisory and the NVD record carry the same text, so this is a single source of information rather than independent confirmation.
What happened
The flaw sits in the router's web management code. The advisory names the function sub_14914 in the file /cgi-bin/mainfunction.cgi and says that manipulating the argument swmconfigupload leads to command injection. The record was published on November 15, 2026, and the weakness is classed as CWE-74 and CWE-77.
The advisory states that the exploit has been disclosed publicly and may be used. Its references include a GitHub repository of Vigor2960 security analysis cases, plus several VulDB pages. We have not reproduced or described any attack technique here, and you do not need one to protect your devices.
Technical details in plain terms
Command injection happens when a program builds an operating system command from input it received and does not properly separate the data from the command. Someone who controls that input may be able to make the device run commands the author never intended.
The CVSS v4 metrics in the advisory rate confidentiality, integrity and availability impact as High, both for the vulnerable system and for subsequent systems. The same metrics describe a network attack vector, low attack complexity, no attack requirements, no user interaction and low privileges required.
That last point matters. The name of the linked case in the GitHub repository includes the word authenticated, which suggests an attacker may need a valid login first. The advisory text itself does not spell out an authentication requirement, so treat the exact precondition as not fully confirmed. Even if a login is needed, weak, stolen or default credentials on an internet-facing admin page are a common problem, so the risk remains real.
Who is affected
- Any Vigor2960 running firmware 1.5.1.6 or earlier.
- Devices whose web management interface can be reached from the internet or from untrusted internal networks, since the advisory describes the issue as remotely exploitable.
- Environments where the router sits between networks or handles VPN traffic, because the CVSS metrics rate the impact on subsequent systems as High.
- Managed service providers and agencies that deploy these units for clients and may not track their firmware.
The vendor comment quoted in the advisory says 1.5.1.6 is not the latest version for the 2960, that the latest version fixes many security issues, and that another release in their plan should solve the reported issues. That suggests further fixes may follow, so keep watching DrayTek's published firmware and notices after you upgrade.
How to check your exposure
Log in to the router's admin interface from a trusted network and read the firmware version on the dashboard or system status page. Anything at or below 1.5.1.6 is in the affected range.
Then check whether the admin interface is reachable from outside. From a machine on a different network, such as a mobile hotspot, the command below only attempts a connection and prints the HTTP response headers. Replace the placeholder with your router's public address, and add the port your management interface uses if it is not the default.
curl -I --max-time 10 https://ROUTER_PUBLIC_IP_OR_HOSTNAME/If you get a response, the management page is exposed and should be restricted regardless of firmware version. A timeout or refused connection is the result you want to see.
What to do now
- Record the current firmware version of every Vigor2960 you manage.
- Download firmware 1.5.1.7 from the firmware link in the advisory and consult DrayTek's documentation for the upgrade procedure for your model.
- Back up the router configuration before upgrading, and schedule the upgrade for a maintenance window.
- Disable remote administration from the WAN, or limit it to a VPN or a short list of trusted IP addresses.
- Change administrator passwords to long, unique values and remove accounts you do not use.
- After upgrading, confirm the new version in the admin interface and review the configuration for changes you did not make, such as new users, port forwards or DNS settings.
- Keep an eye out for the additional release the vendor says is planned.
Detection and monitoring
The research does not describe specific indicators of compromise for this flaw, so the following are general suggestions. Review the router's system and admin logs, if available, for logins you do not recognize, configuration changes or uploads you did not perform, and unexplained reboots. Compare the current configuration with your last known good backup.
If anything looks wrong, treat the device as compromised: restore a clean configuration and rotate every credential and pre-shared key that passed through it. A recovery process such as website hacked: what to do can help, and small business website security covers general basics.
For the sites and services behind the router, Webforta Monitor can alert you to uptime, certificate and DNS changes, which can be an early visible sign of a network-edge problem. It does not inspect or patch the router itself.
What is still unknown
- Whether attackers are exploiting this in the wild. The advisory says the exploit has been disclosed publicly, but it does not report active attacks, and the research shows no CISA KEV listing.
- The exact authentication requirement. The CVSS metrics say low privileges and the linked case name says authenticated, but the advisory text does not state it.
- Whether later firmware will change the fix, given the vendor's note about an upcoming release.
- The GitHub entry is marked unreviewed and lists affected and patched versions as unknown in its metadata; the version details above come from its description text.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
