CVE-2020-8515
This CVE is being exploited. Apply the vendor fix, or take the service off the internet until you can, then check your logs for attempts.
What it is
DrayTek Vigor2960 1.3.1_Beta, Vigor3900 1.4.4_Beta, and Vigor300B 1.3.3_Beta, 1.4.2.1_Beta, and 1.4.4_Beta devices allow remote code execution as root (without authentication) via shell metacharacters to the cgi-bin/mainfunction.cgi URI. This issue has been fixed in Vigor3900/2960/300B v1.5.1.
Live exploitation on the huntback network (30 days)
Detection
Evidence
Confirmed exploited. Our decoys saw 5 exploitation attempts in the last 14 days; CISA added it to KEV 1835 days ago.
Last attempt. 12 attempts on our decoys, 5 in the last 14 days
First exploitation attempt on our decoys
Added to CISA Known Exploited Vulnerabilities
Published
Exploit code published (ExploitDB)
Nuclei detection template available
Observed: our own decoys saw it. Reported: CISA, the vendor or another named source says so. Weaponised: public exploit code or a scanner template exists. Methodology
Questions
Is CVE-2020-8515 being exploited in the wild?
Yes. The huntback decoy network captured 12 exploitation attempts from 7 distinct source IPs; the most recent was on 2026-11-11. It is also in the CISA KEV catalogue.
Can CVE-2020-8515 be detected on the network?
Yes. huntback carries a network signature for CVE-2020-8515, so attempts against a decoy are tagged in real time.
How huntback helps
Deploy a decoy that emulates Vigor2960 and you will see every attempt at this CVE the moment it lands, with the full payload, the attacker's infrastructure, and any stage-2 loader. Then huntback can scan the attacker back.
Related
NVD record → Browse all CVEs → Live malware and C2 finds → Novel-attack discovery → Deploy a decoy →API
This record, with its evidence timeline, as JSON:
curl -H "X-API-Key: $HUNTBACK_KEY" https://app.huntback.io/api/v1/evidence/CVE-2020-8515