Skip to main content
VulnerabilityPublished Updated

CVE-2023-25583: Milesight UR32L · OS Command Injection

Affects Milesight UR32LSource CVE Database V5

0

Not known to be exploited · CVSS 7.2 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
7.2High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.5% chance of exploitation in 30 days – higher than 89% 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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2023

  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

Affected software

ProductAffectedFixed in
Milesight UR32LAffected
  • =32.3.0.5
Fixed in–

AI-suggested

Organizations should immediately inventory their network to identify any Milesight UR32L devices running firmware version 32.3.0.5. Since no official patches are currently linked, it is critical to monitor vendor communications for firmware updates addressing this vulnerability. In the interim, restrict network access to the management interfaces of affected devices using network segmentation, access control lists (ACLs), and VPNs to limit exposure to trusted administrators only. Employ strict authentication and authorization controls to ensure only privileged users can configure VLAN settings. Implement network intrusion detection/prevention systems (IDS/IPS) with signatures or anomaly detection to identify and block suspicious command injection attempts targeting the zebra vlan_name functionality. Regularly audit device configurations and logs for signs of unauthorized access or command execution. Additionally, consider deploying network segmentation and zero-trust principles to minimize the impact of potential device compromise.

Description

Two OS command injection vulnerabilities exist in the zebra vlan_name functionality of Milesight UR32L v32.3.0.5. A specially crafted network request can lead to command execution. An attacker can send a network request to trigger these vulnerabilities.This command injection is in the code branch that manages a new vlan configuration.

References

Community reviews

Loading reviews…