CVE-2023-35194: Peplink Surf SOHO HW1 · OS Command Injection
Affects Peplink Surf SOHO HW1Source CVE Database V5
Not known to be exploited · CVSS 7.2 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 5.4% chance of exploitation in 30 days – higher than 92% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 11 Oct 2023
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 2026-10-26.
What to do
AI-suggested
1. Immediately restrict access to the management interface of Peplink Surf SOHO HW1 devices to trusted networks and IP addresses only, using firewall rules or VPNs. 2. Enforce strong authentication mechanisms, including complex passwords and, if supported, multi-factor authentication to reduce risk of credential compromise. 3. Monitor device logs and network traffic for unusual authenticated HTTP requests targeting the api.cgi endpoint, especially those invoking cmd.mvpn.x509.write functionality. 4. Disable or limit the use of vulnerable API functionalities if possible until a vendor patch is released. 5. Regularly audit and rotate administrative credentials to minimize risk from leaked or reused passwords. 6. Engage with Peplink support or vendor channels to obtain and apply firmware updates or patches as soon as they become available. 7. Consider network segmentation to isolate vulnerable devices from critical assets. 8. Educate administrators on the risks of this vulnerability and ensure incident response plans include steps for potential exploitation scenarios.
Description
An OS command injection vulnerability exists in the api.cgi cmd.mvpn.x509.write functionality of peplink Surf SOHO HW1 v6.3.5 (in QEMU). A specially crafted HTTP request can lead to command execution. An attacker can make an authenticated HTTP request to trigger this vulnerability.This vulnerability is specifically for the `system` call in the file `/web/MANGA/cgi-bin/api.cgi` for firmware version 6.3.5 at offset `0x4bde44`.