Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-3040: OS Command Injection in DrayTek Vigor 300B

0
Medium
VulnerabilityCVE-2026-3040cvecve-2026-3040
Published: Mon Feb 23 2026 (02/23/2026, 22:02:07 UTC)
Source: CVE Database V5
Vendor/Project: DrayTek
Product: Vigor 300B

Description

A vulnerability was identified in DrayTek Vigor 300B up to 1.5.1.6. This affects the function cgiGetFile of the file /cgi-bin/mainfunction.cgi/uploadlangs of the component Web Management Interface. The manipulation of the argument File leads to os command injection. The attack may be initiated remotely. The exploit is publicly available and might be used. The vendor confirms that "300B is EoL, and this is an authenticated vulnerability. We don't plan to fix it." This vulnerability only affects products that are no longer supported by the maintainer.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 03/03/2026, 01:21:00 UTC

Technical Analysis

CVE-2026-3040 is a medium-severity OS command injection vulnerability found in the DrayTek Vigor 300B router, affecting firmware versions up to 1.5.1.6. The vulnerability resides in the web management interface component, specifically within the cgiGetFile function of the /cgi-bin/mainfunction.cgi/uploadlangs endpoint. An attacker with authenticated access can manipulate the File parameter to inject and execute arbitrary operating system commands on the device. This can lead to unauthorized command execution, potentially compromising the device's integrity and availability. The attack vector is remote network access to the management interface, but requires valid credentials, limiting ease of exploitation. The vendor has confirmed that the Vigor 300B is end-of-life and will not receive security patches, leaving the vulnerability unmitigated in affected devices. While no active exploitation has been reported, public exploit code is available, increasing the risk of targeted attacks. The vulnerability's CVSS 4.0 score of 5.1 reflects its medium severity, considering the need for authentication and limited impact scope. Organizations using this device should be aware that continued use exposes them to potential compromise, especially if credentials are leaked or weak. The lack of vendor support necessitates alternative mitigation approaches such as device replacement or strict network controls.

Potential Impact

The primary impact of CVE-2026-3040 is unauthorized remote command execution on affected DrayTek Vigor 300B devices, which can lead to device compromise, disruption of network services, and potential pivoting to internal networks. Since the vulnerability requires authentication, the risk is somewhat mitigated by credential controls; however, if credentials are weak, reused, or compromised, attackers can exploit this flaw to gain control over the device. This can result in loss of device integrity, potential denial of service, or use of the device as a foothold for further attacks within an organization's network. The fact that the product is end-of-life and will not receive patches means that organizations cannot remediate the vulnerability via firmware updates, increasing long-term risk. The availability of public exploit code further raises the likelihood of exploitation attempts. Organizations relying on these devices for critical network functions may face operational disruptions and increased exposure to cyberattacks.

Mitigation Recommendations

Given the vendor's decision not to patch this vulnerability due to end-of-life status, organizations should prioritize replacing DrayTek Vigor 300B devices with supported models that receive security updates. Until replacement is feasible, organizations should implement strict network segmentation to isolate these devices from critical infrastructure and limit access to the management interface to trusted administrators only. Enforce strong, unique authentication credentials and consider multi-factor authentication if supported. Monitor device logs and network traffic for suspicious activity indicative of exploitation attempts. Disable remote management access if not required, or restrict it via VPN or IP whitelisting. Regularly audit devices for unauthorized configuration changes. If replacement is delayed, consider deploying intrusion detection/prevention systems (IDS/IPS) tuned to detect exploitation attempts targeting this vulnerability. Maintain an inventory of affected devices to ensure focused mitigation efforts.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
VulDB
Date Reserved
2026-02-23T16:34:06.326Z
Cvss Version
4.0
State
PUBLISHED

Threat ID: 699cd1ebbe58cf853bd0c5a1

Added to database: 2/23/2026, 10:17:15 PM

Last enriched: 3/3/2026, 1:21:00 AM

Last updated: 4/9/2026, 11:34:20 PM

Views: 103

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses