An issue in Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.9.8.8, Vigor 2860/2925 prior to v3.9.7, Vigor 2862
Noroxi assessment
Priority: Monitor (action score 33/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.21% (FIRST EPSS).
- Someone with local access to the system can trigger it. No account or password is required. No user action is required. No special conditions are required; it is repeatable.
- According to the record, no fixed version is available yet.
Low priority for now. Update when a fix is released; follow the vendor's advisory.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
An issue in Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.9.8.8, Vigor 2860/2925 prior to v3.9.7, Vigor 2862/2926 prior to v3.9.9.4, Vigor 2133/2762/2832 prior to v3.9.8, Vigor 2135/2765/2766 prior to v4.4.5.1, Vigor 2865/2866/2927 prior to v4.4.5.3, Vigor 2962/3910 prior to v4.3.2.7, Vigor 3912 prior to v4.3.5.2, and Vigor 2925 up to v3.9.6 allows attackers to upload crafted APP Enforcement modules, leading to arbitrary code execution.
- Published
- Feb 27, 2025
- Updated
- Jul 5, 2026
- EPSS
- 0.2% · 11th percentile
- CWE
- CWE-434
Report tools
Action score
33
Monitor
Low priority for now.
- CVSS
- 33 / 40 · 8.4 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
Vulnrichment: CISA's decision-tree inputs.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- No fixed version yet
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| draytek | vigor165 firmware | cpe:2.3:o:draytek:vigor165_firmware |
| draytek | vigor165 | cpe:2.3:h:draytek:vigor165 |
| draytek | vigor166 firmware | cpe:2.3:o:draytek:vigor166_firmware |
| draytek | vigor166 | cpe:2.3:h:draytek:vigor166 |
| draytek | vigor2620 firmware | cpe:2.3:o:draytek:vigor2620_firmware |
| draytek | vigor2620 | cpe:2.3:h:draytek:vigor2620 |
| draytek | vigorlte200 firmware | cpe:2.3:o:draytek:vigorlte200_firmware |
| draytek | vigorlte200 | cpe:2.3:h:draytek:vigorlte200 |
| draytek | vigor2860 firmware | cpe:2.3:o:draytek:vigor2860_firmware |
| draytek | vigor2860 | cpe:2.3:h:draytek:vigor2860 |
| draytek | vigor2925 firmware | cpe:2.3:o:draytek:vigor2925_firmware |
| draytek | vigor2925 | cpe:2.3:h:draytek:vigor2925 |
and 28 more
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- draytek vigor165 firmwarebefore 4.2.7
- draytek vigor166 firmwarebefore 4.2.7
- draytek vigor2133 firmwarebefore 3.9.9
- draytek vigor2135 firmwarebefore 4.4.5.1
- draytek vigor2620 firmwarebefore 3.9.8.9
- draytek vigor2762 firmwarebefore 3.9.9
- draytek vigor2765 firmwarebefore 4.4.5.1
- draytek vigor2766 firmwarebefore 4.4.5.1
- draytek vigor2832 firmwarebefore 3.9.9
- draytek vigor2860 firmwarebefore 3.9.8
- draytek vigor2862 firmwarebefore 3.9.9.5
- draytek vigor2865 firmwarebefore 4.4.5.3
- draytek vigor2866 firmwarebefore 4.4.5.3
- draytek vigor2925 firmwarebefore 3.9.8
- draytek vigor2926 firmwarebefore 3.9.9.5
- draytek vigor2927 firmwarebefore 4.4.5.3
- draytek vigor2962 firmwarebefore 4.3.2.8
- draytek vigor2962 firmware4.4.3.0
- draytek vigor3910 firmwarebefore 4.3.2.8
- draytek vigor3910 firmware4.4.3
Same product
draytek: all recordsOther highest-scoring records for the same primary product.
- CVE-2024-41339An issue in the CGI endpoint used to upload configurations in Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.35Monitor
- CVE-2024-41338A NULL pointer dereference in Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.9.8.8, Vigor 2860/2925 prior to 30Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
No fix version is recorded for this entry. Check the references for vendor advisories.
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
No credits in the CNA record.
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2024-413390 days apartAn issue in the CGI endpoint used to upload configurations in Draytek devices Vigor 165/166 prior to v4.2.6 , Vigor 2620/LTE200 prior to v3.35Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
No known public program.
Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).
Technical details
Attack conditions
- Someone with local access to the system can trigger it.
- No account or password is required.
- No user action is required.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- high · data can be read
- Integrity
- high · data or configuration can be modified
- Availability
- high · the service can be disrupted
- Attack vector
- Local
- Attack complexity
- Low
- Privileges required
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality impact
- High
- Integrity impact
- High
- Availability impact
- High
Weakness class (CWE)
CWE-434 · Unrestricted Upload of File with Dangerous TypeCVSS vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
nvd-secondary
Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Attack patterns (CAPEC)
ATT&CK techniques
Change log
No changes recorded on tracked fields yet. Score, KEV, exploit maturity and fix status changes appear here.
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.