Peplink InControl 2 through 2.14.2 before 2026-06-03 allows use of a semicolon to bypass…
Priority HIGH 67CWE-551Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- Low
- User interaction
- None
- Attack complexity
- Low
- Impact type
- —
- Confidentiality · integrity · availability
- High · None · None
- Fix status
- Fixed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA.
Summary
Peplink InControl 2 through 2.14.2 before 2026-06-03 allows use of a semicolon to bypass access-control rules for certain /rest/o/{orgId} endpoints.
Why it matters now
Exploitation Proof of concept CISA SSVC · not in CISA KEV
EPSS 0.00377 31st percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix Fixed InControl (Peplink): 2026-06-03
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- Poc
- Automatable
- No
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
Remediation
- Fix · CNA InControl (Peplink) Fixed in 2026-06-03
Timeline
- 2026-10-02 Threatist record created from CVE-2026-57920
- 2026-10-03 Alias added: GHSA-69xh-mqwf-cxv2
References
Sources
- CVE-2026-57920 · CVE Program
- CVE-2026-57920 · NVD
- FIRST EPSS
- GHSA-69xh-mqwf-cxv2 · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences