Command InjectionWeakness · CWE-77

CVE-2025-24285

CRITICAL · 9.8 CVSS v3.1 Published 2025-08-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Multiple Improper Input Validation vulnerabilities in UniFi Connect EV Station Lite may allow a Command Injection by a malicious actor with network access to the UniFi Connect EV Station Lite. Affected Products: UniFi Connect EV Station Lite (Version 1.5.1 and earlier) Mitigation: Update UniFi Connect EV Station Lite to Version 1.5.2 or later

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The UniFi Connect EV Station Lite contains multiple improper input validation vulnerabilities in its web interface that allow authenticated or unauthenticated attackers with network access to inject and execute arbitrary operating system commands on the underlying Linux system. These command injection flaws stem from insufficient sanitization of user-supplied input fields before passing them to system shell commands.

MitigationUpdate UniFi Connect EV Station Lite firmware to version 1.5.2 or later to patch the command injection vulnerabilities. Network segmentation and restricting access to the device management interface should be implemented as additional compensating controls.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the device model is UniFi Connect EV Station Lite
    Inspect the physical device label or check the UniFi Controller/management interface to verify the exact hardware model
    Affected if The device is not a UniFi Connect EV Station Lite model
  2. Determine the installed firmware version
    Access the UniFi management interface or use the UniFi Controller to check the current firmware version of the EV Station Lite device
    Affected if The firmware version is 1.5.1 or earlier (versions prior to the 1.5.2 patch)
  3. Verify the UniFi Connect web interface is enabled
    Check if the web-based management interface for the EV Station Lite is accessible on the network (typically ports 80/443 or the UniFi Controller ports)
    Affected if The web management interface is enabled and network-accessible (the vulnerability is in the web interface input validation)
  4. Assess network exposure of the management service
    Determine if the EV Station Lite management interface is exposed to untrusted networks or the internet, or if it accepts connections from unauthenticated sources
    Affected if The interface is reachable from untrusted network segments or unauthenticated actors can reach it

A user is affected if they are running UniFi Connect EV Station Lite firmware version 1.5.1 or earlier with the web management interface network-accessible

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update UniFi Connect EV Station Lite firmware to version 1.5.2 or later to patch the command injection vulnerabilities. Network segmentation and restricting access to the device management interface should be implemented as additional compensating controls.

Recommended fix High confidence

Version 1.5.2 or later

  1. Access the UniFi Connect controller or web interface managing the EV Station Lite device
  2. Navigate to the device settings or management section for UniFi Connect EV Station Lite
  3. Verify the current firmware/software version is 1.5.1 or earlier
  4. Locate the firmware/software update option within the device settings
  5. Update the UniFi Connect EV Station Lite to version 1.5.2 or later
  6. Confirm the update was successful and verify the new version number

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-24285 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-24285 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data