LiveActive security incident?Get immediate response
CVE Record

CVE-2020-10826: /cgi-bin/activate.cgi on Draytek Vigor3900, Vigor2960, and Vigor300B devices before 1.5.1 allows remote att...

/cgi-bin/activate.cgi on Draytek Vigor3900, Vigor2960, and Vigor300B devices before 1.5.1 allows remote attackers to achieve command injection via a remote HTTP request in DEBUG mode.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2020-10826 is a critical DrayTek router vulnerability affecting Vigor3900, Vigor2960, and Vigor300B devices before firmware 1.5.1. A remote attacker could inject commands through a CGI endpoint when DEBUG mode is enabled, potentially taking control of the device.

Executive priority

Treat this as urgent for any exposed or legacy DrayTek edge device. The business risk is device compromise at the network perimeter, which can affect traffic confidentiality, availability, and downstream security controls.

Technical view

The CVE describes command injection in /cgi-bin/activate.cgi, reachable by remote HTTP request in DEBUG mode. CVSS 3.1 is 9.8, with network access, low complexity, no privileges, no user interaction, and high confidentiality, integrity, and availability impact.

Likely exposure

Exposure is most likely on DrayTek Vigor3900, Vigor2960, or Vigor300B appliances running firmware before 1.5.1, especially where HTTP management or related CGI paths are reachable from untrusted networks and DEBUG mode is enabled.

Exploitation context

The provided sources support remote unauthenticated exploitability under the DEBUG-mode condition. The source bundle does not state active exploitation, and KEV is false, so active exploitation should not be claimed from this evidence.

Researcher notes

Evidence is limited to the CVE description and linked references. The CVE’s affected CPE data is not populated, so product scoping should be validated through asset inventory and DrayTek firmware records. Do not assume exploitation beyond the DEBUG-mode condition.

Mitigation direction

  • Upgrade affected Vigor3900, Vigor2960, and Vigor300B firmware to 1.5.1 or later.
  • Disable DEBUG mode where it is enabled.
  • Remove public HTTP management exposure where operationally possible.
  • Check DrayTek advisory and current vendor guidance for device-specific remediation.
  • Isolate or replace appliances that cannot be updated to fixed firmware.

Validation and detection

  • Inventory Vigor3900, Vigor2960, and Vigor300B appliances and record firmware versions.
  • Confirm no affected appliance is running firmware earlier than 1.5.1.
  • Verify DEBUG mode is disabled on in-scope devices.
  • Check whether management HTTP endpoints are reachable from untrusted networks.
  • Review logs for unexpected access to /cgi-bin/activate.cgi if available.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-77: Command execution behavior lookup

Command injection weaknesses can lead defenders to review execution techniques and command interpreter telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Execution behavior lookup

The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-10826 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2020-10826Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-77 · source CWE mapping

Improper Neutralization of Special Elements used in a Command ('Command Injection')

Improper Neutralization of Special Elements used in a Command ('Command Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.