Skip to main content
VulnerabilityPublished Updated

CVE-2023-24519: Milesight UR32L · Command Injection

Affects Milesight UR32LSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 10:12 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.6% 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:L/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

  1. Immediately restrict network access to the vulnerable UR32L devices by implementing strict firewall rules and network segmentation to limit exposure to trusted management networks only.
  2. Monitor network traffic for unusual or malformed requests targeting the ping utility or vtysh_ubus service to detect potential exploitation attempts.
  3. Disable or restrict access to the vulnerable ping tool functionality if possible, until a vendor patch is available.
  4. Engage with the vendor for timely updates or patches and apply them as soon as they are released.
  5. Conduct thorough audits of all Milesight UR32L devices in the environment to identify affected versions and prioritize remediation.
  6. Employ intrusion detection/prevention systems (IDS/IPS) with signatures or heuristics capable of detecting command injection attempts targeting this vulnerability.
  7. Train network administrators on the risks and signs of exploitation related to this vulnerability to improve incident response readiness.

Description

Two OS command injection vulnerability exist in the vtysh_ubus toolsh_excute.constprop.1 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 ping tool utility.

References

Community reviews

Loading reviews…