basicsecurity.net
Proof, not just disclosure.
Threats / DrayTek / CVE-2024-12987
CVE-2024-12987 · EUVD no mirror located · GCVE no mirror located Verified 2026-08-04

DrayTek Vigor Routers vulnerability

DrayTek Vigor routers contain an OS command injection vulnerability in the web management interface that allows unauthenticated remote code execution.

Verdict

Today item — known-exploited.

A command injection flaw in the /cgi-bin/mainfunction.cgi/apmcfgupload endpoint of DrayTek Vigor2960, Vigor300B, and Vigor3900 routers enables attackers to execute arbitrary OS commands with router privileges, leading to full device compromise.

CISA KEV Yes · 2025-05-155EPSS 0.98084 (verify live)6CVSS 6.93CISA SSVC Exploitation: active · Automatable: yes · Impact: total4Exploit Public PoC / detection · nuclei template15
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
82 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
dashboard.shadowserver.o ↗dashboard.shadowserver.o ↗dashboard.shadowserver.o ↗fortinet.com ↗Confirmed
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2025-05-15).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.98084 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
FIRST EPSS ↗High
Severity / affected
CVSS 6.9 (CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N) · Affected: DrayTek, Vigor Routers. Confirm exact fixed builds in the vendor advisory.CVSS — CNA-assigned (CVE.org), version 4.0, set at disclosure.
CVE.org ↗Reported
Weakness (CWE)
Mapped to CWE-78 OS Command Injection, CWE-77 Command Injection — weakness family: Injection.CWE — CNA-assigned (CVE.org); the weakness class drives how the flaw is exploited.
CVE.org ↗Reported
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.
CISA-ADP ↗Reported
Currency of the record
CISA added this to its KEV catalog 139 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.
CISA KEV ↗CVE.org ↗Reported
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.
nuclei ↗Confirmed
WeaknessCWE-78 · OS Command InjectionCWE-77 · Command InjectionInjection
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution 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 board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious HTTP request to the vulnerable apmcfgupload endpoint, injecting OS commands into an unsanitized parameter.
Business
The organization's network perimeter is breached through a trusted infrastructure device.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I execute commands with the router's privilege level to establish persistence and pivot deeper into the network.
Business
Attackers gain a foothold for lateral movement and data exfiltration across internal systems.
3

Lateral reach — past segmentation narrative 3

Attacker
I reconfigure routing rules, DNS settings, or intercept traffic to monitor or redirect network communications.
Business
Network integrity is compromised, enabling man-in-the-middle attacks and credential harvesting.
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

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 82 reported-exploitation source(s)
  • CVSS 6.9 — CNA-assigned (CVE.org)
  • CISA SSVC triage disposition (CVE.org ADP)
  • CWE weakness mapping — CNA-assigned (CVE.org)
  • Catalogued by VulDB (CNA)
  • Named finder/reporter credit (CVE.org)

    • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
    • Disclosure & credit2
    Catalogued by VulDBCNA
    Credited with finding itnetsecfish (VulDB User)reporter