cve.bz

CVE-2026-71932 draytek corporation: Path traversal

6.9 mediumEPSS 1.0%

Medium (6.9) in draytek corporation. EPSS 1.0% estimated probability of exploitation activity in the next 30 days.

On this page
Multiple DrayTek VigorSwitch models contain a directory traversal vulnerability in the getSyslogFile function. The vulnerability is caused by insufficient validation of the option field. A remote attacker can trigger this vulnerability via crafted input containing path traversal sequences to access arbitrary files on the device. Exploitation requires valid administrative credentials for the device's web management interface.

Severity

CVSS 4.0

6.9 medium
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

CVSS 3.1

4.9 medium
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N
EPSS
1.0% (unchanged from 1.0% a week ago; 1.0% 30 days ago) estimated probability of exploitation activity in the next 30 days; 65th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: partial, assessed 2026-08-24. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-22 Improper Limitation of a Pathname to a Restricted Directory (Path traversal)
OWASP Top 10
A01:2025 Broken Access Control
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-71932 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-71932?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-71932?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-71932 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

  • draytek corporation:vigorswitch fx2120
  • draytek corporation:vigorswitch g1280
  • draytek corporation:vigorswitch g1282
  • draytek corporation:vigorswitch g2100
  • draytek corporation:vigorswitch g2121
  • draytek corporation:vigorswitch g2280x
  • draytek corporation:vigorswitch g2282x
  • draytek corporation:vigorswitch g2540x
  • draytek corporation:vigorswitch g2540xs
  • draytek corporation:vigorswitch g2542x
  • draytek corporation:vigorswitch p1280
  • draytek corporation:vigorswitch p1281x
  • draytek corporation:vigorswitch p1282
  • draytek corporation:vigorswitch p2100
  • draytek corporation:vigorswitch p2121
  • draytek corporation:vigorswitch p2280x
  • draytek corporation:vigorswitch p2282x
  • draytek corporation:vigorswitch p2540x
  • draytek corporation:vigorswitch p2540xs
  • draytek corporation:vigorswitch p2542x
  • draytek corporation:vigorswitch p2542xh
  • draytek corporation:vigorswitch pq2121x
  • draytek corporation:vigorswitch pq2200xb
  • draytek corporation:vigorswitch pq2300xb
  • draytek corporation:vigorswitch px2060
  • draytek corporation:vigorswitch q2121x
  • draytek corporation:vigorswitch q2200x
  • draytek corporation:vigorswitch q2300x

Versions

From the CNA's record in the CVE List.

ProductAffected
DrayTek Corporation VigorSwitch G2540xsbefore 3.9.10
DrayTek Corporation VigorSwitch P2540xsbefore 3.9.10
DrayTek Corporation VigorSwitch FX2120before 3.9.10
DrayTek Corporation VigorSwitch G2282xbefore 2.10.6
DrayTek Corporation VigorSwitch P2282xbefore 2.10.6
DrayTek Corporation VigorSwitch Q2300xbefore 2.10.7
DrayTek Corporation VigorSwitch PQ2300xbbefore 2.10.7
DrayTek Corporation VigorSwitch G2542xbefore 3.10.6
DrayTek Corporation VigorSwitch P2542xbefore 3.10.6
DrayTek Corporation VigorSwitch P2542xhbefore 3.10.6
DrayTek Corporation VigorSwitch PX2060before 2.9.10
DrayTek Corporation VigorSwitch G1280before 2.9.10
DrayTek Corporation VigorSwitch P1280before 2.9.10
DrayTek Corporation VigorSwitch P1281xbefore 2.9.10
DrayTek Corporation VigorSwitch G1282before 2.9.10
DrayTek Corporation VigorSwitch P1282before 2.9.10
DrayTek Corporation VigorSwitch G2121before 2.9.10
DrayTek Corporation VigorSwitch P2121before 2.9.10
DrayTek Corporation VigorSwitch PQ2121xbefore 2.9.10
DrayTek Corporation VigorSwitch Q2121xbefore 2.9.10
DrayTek Corporation VigorSwitch G2280xbefore 2.9.10
DrayTek Corporation VigorSwitch P2280xbefore 2.9.10
DrayTek Corporation VigorSwitch Q2200xbefore 2.9.10
DrayTek Corporation VigorSwitch PQ2200xbbefore 2.9.10
DrayTek Corporation VigorSwitch G2100before 2.9.10
DrayTek Corporation VigorSwitch P2100before 2.9.10
DrayTek Corporation VigorSwitch G2540xbefore 2.9.10
DrayTek Corporation VigorSwitch P2540xbefore 2.9.10

Attack patterns (CAPEC)

  • CAPEC-64 Using Slashes and URL Encoding Combined to Bypass Validation Logic Likelihood: High · Severity: High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-78 Using Escaped Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-79 Using Slashes in Alternate Encoding Likelihood: High · Severity: High
  • CAPEC-126 Path Traversal Likelihood: High · Severity: Very High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON