CVE-2024-43027: DrayTek Vigor · Command Injection
Source CVE Database V5
Not known to be exploited · CVSS 8.0 High.
Data as of 26 Oct 2026, 17:16 UTC
- EPSS
- 1.2% chance of exploitation in 30 days – higher than 70% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 21 Aug 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Upgrade affected DrayTek Vigor devices to firmware version v1.5.1.5_Beta or later as soon as the patch becomes available from the vendor.
- Restrict access to the device management interfaces (especially cgi-bin endpoints) to trusted IP addresses and networks using firewall rules or VPNs.
- Enforce strong, unique administrative credentials and disable any default or unused accounts.
- Monitor device logs and network traffic for unusual command execution patterns or unauthorized access attempts.
- Implement network segmentation to isolate management interfaces from general user networks.
- Consider disabling web management interfaces if not required or use alternative secure management methods such as SSH with key-based authentication.
- Stay informed on vendor advisories and threat intelligence for any emerging exploits or additional mitigations.
Description
DrayTek Vigor 3900 before v1.5.1.5_Beta, DrayTek Vigor 2960 before v1.5.1.5_Beta and DrayTek Vigor 300B before v1.5.1.5_Beta were discovered to contain a command injection vulnerability via the action parameter at cgi-bin/mainfunction.cgi.