Skip to main content

DrayTek Vigor2960 CVE-2026-113393

| EUVDEUVD-2026-105001 LOW
Unrestricted Upload of File with Dangerous Type (CWE-434)
2026-10-20 VulDB GHSA-hghw-mj7p-r942
2.1
CVSS 4.0 · Vendor: VulDB
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain valid low-priv web credentials
  2. Delivery
    Send crafted request to mainfunction.cgi commonupload
  3. Exploit
    Manipulate upload_path/upload_name arguments
  4. Execution
    Clobber/write arbitrary file on device
  5. Impact
    Degrade integrity of router files

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V5 - File Handling File type validation, storage isolation
MITRE ATT&CK

2 techniques across 2 tactics: Command and Control, Persistence

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires an authenticated session (PR:L) on the DrayTek Vigor2960 web management interface, after which the attacker reaches the commonupload function of /cgi-bin/mainfunction.cgi and manipulates the upload_path and upload_name parameters to perform an unrestricted/arbitrary file upload (CWE-434), specifically arbitrary file clobber per the public case. LIMITING FACTORS: valid credentials are mandatory (no unauthenticated path), the flaw is specific to firmware 1.5.1.6 Revision 8218 on the Vigor2960, and the device is end-of-sale with only v1.5.1.7 remediating it - exposure is confined to environments still running the vulnerable firmware with the web interface reachable by the attacker.

Impact

This is a moderate-risk, authenticated file-upload flaw rather than a top-priority emergency. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) confirms network-reachable, low-complexity exploitation but requires at least low-level privileges (PR:L), meaning a valid authenticated session on the Vigor2960 web management interface is a prerequisite - this materially lowers mass-exploitation potential versus an unauthenticated flaw. Impact is bounded: all three impact metrics are Low (VC:L/VI:L/VA:L), and the public exploit case is explicitly labeled 'authenticated-commonupload-arbitrary-file-clobber,' indicating arbitrary file overwrite/clobber rather than confirmed remote code execution, which is consistent with the modest 5.3 score. A public POC exists (E:P / GitHub), but there is NO CISA KEV listing and NO EPSS score provided in the input, so exploitation probability cannot be quantified and there is no evidence of active in-the-wild use - the POC and active-exploitation signals must not be conflated. Net: real but secondary priority, elevated by EoS status (DrayTek states the 2960 is end-of-sale with only major/unauthenticated issues reviewed), which means residual authenticated issues like this may linger unpatched in the field.

Exploit ScenarioDerived

An attacker who already holds valid (even low-privileged) credentials to the Vigor2960 web administration interface sends a crafted request to /cgi-bin/mainfunction.cgi against the commonupload component, manipulating the upload_path/upload_name arguments to write or overwrite files at an attacker-chosen location on the device. A public proof-of-concept exists (yikesoftware DRV2960-0010), lowering the skill barrier; low attack complexity (AC:L) and no user interaction make the authenticated step the main gate.

Monitor Track and reassess. Why: Vendor states no customer action required.
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 20, 2026

Authenticated remote attackers can exploit an unrestricted file-upload flaw in DrayTek Vigor2960 firmware 1.5.1.6 Revision 8218 by manipulating the upload_path and upload_name parameters in the commonupload function of /cgi-bin/mainfunction.cgi, resulting in arbitrary file clobber on the device. Publicly available exploit code exists, but exploitation requires valid credentials and access to the web management interface, keeping the issue moderate-risk rather than an emergency. DrayTek addressed the flaw in firmware 1.5.1.7; because the Vigor2960 is end-of-sale with limited support, exposure is limited to units still running the vulnerable release.

RemediationAI

Upgrade the Vigor2960 to firmware 1.5.1.7 using DrayTek's archive at https://fw.draytek.com.tw/Vigor2960/Firmware/v1.5.1.7/Vigor2960_v1.5.1.7.zip; this is the vendor-released fix and the only version identified as remediating the flaw. Because the device is end-of-sale with limited vendor support, plan replacement if 1.5.1.7 cannot be maintained. If upgrading is not immediately possible, remove WAN exposure of the web management interface, restrict /cgi-bin/mainfunction.cgi and administrative access to a trusted management VLAN or IP allowlist, and rotate credentials for accounts that can reach the UI; these controls lower the chance of authenticated exploitation but do not correct the upload validation weakness. Also monitor for unexpected file changes and review logs for unusual POST requests to the commonupload handler.

Affected VersionsENISA

Vigor2960 1.5.1.6 Revision 8218

Affects your stack

Find out whether the stacks and servers you run are on an affected version.

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The DrayTek Vigor2960 is a router/security gateway with a CGI-based web management interface served through /cgi-bin/mainfunction.cgi. The commonupload routine accepts upload_path and upload_name parameters and fails to sufficiently restrict the destination path or filename, placing the issue in the CWE-434 unrestricted upload class; the public case describes the practical effect as arbitrary file clobber. Exploitation occurs over HTTP(S) against the management interface and, per the assessed vector, requires a valid authenticated session (PR:L). The affected build is 1.5.1.6 Revision 8218, and CPE data confirms the DrayTek Vigor2960 product family. Because the device is end-of-sale, firmware 1.5.1.7 is the remediation boundary.

Know when Vigor2960 gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulDB) PRIMARY 2.1 MEDIUM
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P
vuln.today AI 6.3 MEDIUM

Network-reachable low-complexity upload needs a valid login (PR:L), and arbitrary file clobber yields limited confidentiality, integrity and availability impact (C/I/A:L).

3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N

Primary rating from Vendor (VulDB).

CVSS VectorVendor: VulDB

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
Low
User Interaction
None
Vulnerable system: Confidentiality
Low
Vulnerable system: Integrity
Low
Vulnerable system: Availability
Low
Subsequent system: Confidentiality
None
Subsequent system: Integrity
None
Subsequent system: Availability
None

Lifecycle Timeline

3
Severity Changed
Oct 20, 2026 - 14:22 NVD
MEDIUM LOW
CVSS changed
Oct 20, 2026 - 14:22 NVD
5.3 (MEDIUM) 2.1 (LOW)
CVE Published
Oct 20, 2026 - 13:15 cve.org
MEDIUM 5.3

DescriptionCVE.org

A vulnerability was determined in DrayTek Vigor2960 1.5.1.6 Revision 8218. This issue affects some unknown processing of the file /cgi-bin/mainfunction.cgi of the component commonupload. Executing a manipulation of the argument upload_path/upload_name can lead to unrestricted upload. The attack may be performed from remote. The exploit has been publicly disclosed and may be utilized. Upgrading to version 1.5.1.7 is capable of addressing this issue. It is advisable to upgrade the affected component. The vendor explains: "2960 1.5.1.7 has corrected many security issues. And 2960 is EoS with limited support, only major issues would be reviewed(e.g. unauthenticated vuln.)". This vulnerability only affects products that are no longer supported by the maintainer.

Threat Intelligence Overview

EPSS Score
0.4%
Top 73% exploitable
Prevalence
Low
EoS SMB router model from one vendor, limited remaining footprint
Exploit
POC
Public exploit code exists
Social Media
1
Sightings
Data Quality
7 sources
Confidence: High
EUVD NVD CVE.org EPSS Vulnrichment CIRCL GitHub VulDB

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity LOW
CISA KEV No
Public POC Yes
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
Vendor states no customer action required
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Low
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +10
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Malicious file upload attacks exploit insufficient validation when web applications accept user-provided files.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy