Skip to main content
VulnerabilityPublished

CVE-2026-112351: Sunhillo SureLine · OS Command Injection

Affects Sunhillo SureLineSource CVE Database V5

0

Mentioned vulnerabilities

Not known to be exploited · CVSS 8.7 High : upgrade to 9.1.5 soon.

Data as of 27 Oct 2026, 20:12 UTC

CVSS 4.0 base score
8.7High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 9.1.5
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 27 Oct 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 26 Oct 2026.

What to do

Upgrade Sunhillo SureLine to 9.1.5.

Affected software

ProductAffectedFixed in
Sunhillo CorporationSureLineAffected
  • >=8.6.0 <9.1.5
Fixed in
  • 9.1.5

AI-suggested

Upgrade Sunhillo SureLine to version 9.1.5 or later, where this OS command injection vulnerability is fixed. No other mitigations are indicated by the vendor advisory.

Description

Sunhillo SureLine versions from 8.6.0 up to but not including 9.1.5 contain an OS command injection vulnerability in the networkDiag.cgi endpoint. This flaw allows an authenticated remote attacker with any web account to execute arbitrary commands as root by injecting shell metacharacters into the ipAddr or dnsAddr parameters. The vulnerability arises because attackers can bypass a prior character denylist by using URL-encoded newline (%0a) or ampersand (%26) sequences, which act as command separators after decoding in diagnostic modes such as ping, nslookup, or traceroute. The issue is fixed in version 9.1.5.

References

Community reviews

Loading reviews…