Skip to main content
VulnerabilityPublished

CVE-2025-48979: Ubiquiti UISP Application · Command Injection

Affects Ubiquiti UISP ApplicationSource CVE Database V5

0

Not known to be exploited · CVSS 3.4 Low.

Data as of 26 Oct 2026, 12:29 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 28 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

Affected software

ProductAffectedFixed in
Ubiquiti Inc UISP ApplicationAffected
  • =2.4.220
Fixed in–

AI-suggested

  1. Immediate mitigation should focus on restricting local access to UISP servers to trusted personnel only, employing strict access controls and monitoring.
  2. Implement network segmentation to isolate UISP management interfaces from general user networks and the internet.
  3. Monitor logs and system behavior for unusual command executions or privilege escalations indicative of exploitation attempts.
  4. Apply the principle of least privilege rigorously, ensuring users and processes have only the necessary permissions to operate UISP.
  5. Await and promptly apply official patches or updates from Ubiquiti once released.
  6. Conduct internal audits and penetration testing focusing on command injection vectors within UISP environments.
  7. Employ application-layer input validation and filtering where possible to detect or block malicious inputs.
  8. Educate administrators and operators about the risks of local privilege misuse and encourage reporting of suspicious activities. These steps go beyond generic advice by emphasizing access control, monitoring, and proactive internal security hygiene tailored to the UISP context.

Description

An Improper Input Validation in UISP Application could allow a Command Injection by a malicious actor with High Privileges and local access.

References

Community reviews

Loading reviews…