Threats / DrayTek / CVE-2020-15415
CVE-2020-15415
· EUVD no mirror located
· GCVE no mirror located
Verified 2026-08-04
DrayTek Multiple Vigor Routers vulnerability
DrayTek Vigor routers contain an OS command injection vulnerability in the configuration upload function that allows remote code execution through malicious filenames.
Verdict
Today item — known-exploited.
An unauthenticated attacker can inject arbitrary shell commands via specially crafted filenames in configuration uploads, achieving remote code execution on affected Vigor routers. The vulnerability has been observed in active exploitation.
CISA KEV Yes · 2024-09-304EPSS 0.84599 (verify live)5CVSS 9.8 (CISA)3CISA SSVC Exploitation: active · Automatable: yes · Impact: total3Exploit Public PoC / detection · nuclei template12
01
Is it exploitable?
— the evidence, ranked above the scoreReported exploitation
380 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2024-09-30).
Probability (EPSS)
EPSS 0.84599 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
CVSS 9.8 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H) · Affected: DrayTek, Multiple Vigor Routers. Confirm exact fixed builds in the vendor advisory.CVSS — CISA-assigned via the ADP container (CVE.org), version 3.1; the CNA left no metrics, so CISA's own score is used ahead of NVD.
Weakness (CWE)
Mapped to CWE-78 OS Command Injection — weakness family: Injection.CWE assignment from the public NVD record (may be stale); the weakness class drives how the flaw is exploited.
CISA SSVC (triage disposition)
Exploitation: active · Automatable: yes · Technical Impact: totalCISA's own stakeholder-specific triage inputs, published in the CVE record (CISA Coordinator role). NOTE: this is CISA's three decision points; the final Act/Attend/Track decision also requires a Mission & Well-being input not published here, so no overall decision is asserted.
Currency of the record
CISA added this to its KEV catalog 1553 days after the CVE record was published.KEV lag = CISA-KEV dateAdded − CVE.org datePublished; a floor on how long the known-exploited flaw sat in the public record before the federal catalog listed it. Severity/weakness here is CNA- or CISA-assigned (current at disclosure), independent of NVD's analysis backlog.
Public exploit available
Public exploit tooling is catalogued for this CVE (a public proof-of-concept / detection template). Catalog entries: nuclei template. We link the catalog page(s) only — no payload or code is hosted or restated here.Link, never host — the catalog page is the source; basicsecurity.net does not redistribute payloads.
02
Who’s exploiting it?
— attribution turns risk into urgencyAttribution not established
No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.
03
Why it matters
— the attack path, told twice: adversary, then board1
Front door — unauthenticated access narrative 1
Attacker
I craft a malicious configuration file with shell metacharacters embedded in the filename and upload it with text/x-python-script content type.
Business
The router executes arbitrary commands with device privileges, compromising network infrastructure integrity.
2
Keys to the kingdom — privilege/identity takeover narrative 2
Attacker
I gain code execution to establish persistence, modify routing rules, or pivot to internal network segments.
Business
Attackers obtain sustained access to critical network perimeter devices, enabling lateral movement and data exfiltration.
3
Lateral reach — past segmentation narrative 3
Attacker
I reconfigure the router to intercept, redirect, or monitor network traffic passing through the device.
Business
Confidentiality and integrity of all network communications transiting the router are compromised.
04
What to do
— defensible action- Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05