CVE-2023-35193: 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 25 Oct 2026, 19:02 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-25.
What to do
AI-suggested
To mitigate CVE-2023-35193, European organizations should implement the following specific measures: 1) Monitor Peplink’s official channels for firmware updates or patches addressing this vulnerability and apply them promptly once available. 2) Restrict management interface access to trusted networks and IP addresses using firewall rules and VPNs to reduce exposure. 3) Enforce strong authentication mechanisms, including complex passwords and multi-factor authentication, to prevent unauthorized access to device management. 4) Regularly audit and rotate credentials used for device administration to minimize risk from credential compromise. 5) Implement network segmentation to isolate Peplink devices from critical internal systems, limiting potential lateral movement. 6) Deploy intrusion detection/prevention systems (IDS/IPS) to monitor for anomalous authenticated HTTP requests targeting the api.cgi endpoint. 7) Conduct regular security assessments and penetration testing focusing on network edge devices to identify and remediate similar vulnerabilities. 8) Maintain comprehensive logging and alerting on device management activities to detect suspicious behavior early. These steps go beyond generic advice by focusing on access control hardening, monitoring, and proactive patch management tailored to the specific device and vulnerability context.
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 0x4bddb8.