CVE-2026-129451 · Vendor
NO FIX YET · SEE WHAT TO DO
DrayTek Vigor2960 routers up to firmware 1.5.1.6 have a path traversal flaw in the app_guest_export function of /cgi-bin/mainfunction.cgi, where the filename argument is not sanitized. A remote attacker can use it to reach files outside the intended directory, and a public exploit has been published.
first public Nov 15, 2026 · 1 source
Check it with your coding agent
It reads this page and tells you if your code or app is affected.
Organisations running DrayTek Vigor2960 routers on firmware 1.5.1.6 or earlier, especially with the web management interface reachable from the internet. The sources do not say whether the flaw is reachable on default settings. Teams without Vigor2960 units can skip it.
Not affected if firmware-1.5.1.7-or-later, management-not-internet-exposed, other-draytek-models
Who cares draytek, network-gear, routers, vigor2960
1.5.1.6 or earlier./cgi-bin/mainfunction.cgi exposed to the internet on the router's management interface.1.5.1.7 (per the NVD description). The vendor's statement says 1.5.1.6 is not the latest and a further release is planned.A flaw has been found in DrayTek Vigor2960 up to 1.5.1.6. This affects the function app_guest_export of the file /cgi-bin/mainfunction.cgi. This manipulation of the argument filename causes path traversal. The attack can be initiated remotely. The exploit has been published and may be used. Upgrading to version 1.5.1.7 is able to mitigate this issue. The affected component should be upgraded. 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."
This page as .md · .json · 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/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.
InfraStack checks it against your stack and answers on your report, with the evidence and the fix.