Skip to main content
VulnerabilityPublished

CVE-2025-31713: Unisoc (Shanghai) Technologies SL8521E/SL8521ET/ SL8541E/UIS8141E/UWS6137/UWS6137E/UWS6151(E)/UWS6152 · Command Injection

Affects Unisoc (Shanghai) Technologies SL8521E/SL8521ET/ SL8541E/UIS8141E/UWS6137/UWS6137E/UWS6151(E)/UWS6152Source CVE Database V5

0

Not known to be exploited · CVSS 8.4 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.7% chance of exploitation in 30 days – higher than 53% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Aug 2025

  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

AI-suggested

European organizations should implement targeted mitigation strategies beyond generic advice: 1) Conduct an inventory to identify devices using the affected Unisoc chipsets and confirm their operating system versions. 2) Restrict access to engineer mode services by enforcing strict access controls, ideally limiting access to trusted personnel and secure environments only. 3) Employ network segmentation to isolate devices with these chipsets from critical network segments to reduce the risk of local exploitation. 4) Monitor logs and device behavior for unusual command executions or privilege escalations indicative of exploitation attempts. 5) Engage with Unisoc and device manufacturers to obtain patches or firmware updates as soon as they become available and prioritize their deployment. 6) Where patching is not immediately possible, consider disabling engineer mode services if feasible without impacting device functionality. 7) Enhance physical security controls to prevent unauthorized local access to devices. 8) Implement endpoint detection and response (EDR) solutions capable of detecting command injection patterns and privilege escalation activities on affected devices. These steps collectively reduce the attack surface and improve detection and response capabilities.

Description

In engineer mode service, there is a possible command injection due to improper input validation. This could lead to local escalation of privilege with no additional execution privileges needed.

References

Community reviews

Loading reviews…