dbcve.org
Command InjectionWeakness · CWE-77

CVE-2025-48978

HIGH · 7.5 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 →
80/100
Remediation priority · High
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
An Improper Input Validation in EdgeMAX EdgeSwitch (Version 1.11.0 and earlier) could allow a Command Injection by a malicious actor with access to EdgeSwitch adjacent network. Affected Products: EdgeMAX EdgeSwitch (Version 1.11.0 and earlier) Mitigation: Update the EdgeMAX EdgeSwitch to Version 1.11.1 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

A command injection vulnerability in EdgeMAX EdgeSwitch firmware versions 1.11.0 and earlier allows remote attackers to execute arbitrary commands due to improper input validation. The attack requires network-adjacent access to the affected device, and the high CVSS score (7.5) reflects the severe impact of command injection, which can lead to complete device compromise.

MitigationUpdate EdgeMAX EdgeSwitch firmware to version 1.11.1 or later to address the improper input validation vulnerability. Organizations should identify affected devices in their network and schedule firmware updates following vendor release notes and best practices for network device patching.

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
Adjacent
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:A/AC:H/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 device model is EdgeMAX EdgeSwitch
    Access the device web UI or CLI and identify the exact model name. In the web interface, this is typically shown on the dashboard or in System > Device. Via CLI, use commands like 'show system' or 'show version' to display hardware and model information.
    Affected if The device is not an EdgeMAX EdgeSwitch (the CVE only applies to this product line)
  2. Check installed firmware version
    In the web UI, navigate to System > Firmware or the About/Status page to view the current firmware version. Via CLI, use 'show version' or 'system show' to display firmware information. Compare the version number to 1.11.0.
    Affected if The installed firmware version is 1.11.0 or earlier (versions 1.11.1 and later are patched)
  3. Verify network accessibility of management interface
    Confirm the device management interface (web UI or CLI over SSH/Telnet) is reachable from the network. Use ping or port scanning to verify the device IP is accessible. The CVE requires network-adjacent access to exploit.
    Affected if The device management interface is exposed to network-adjacent attackers (even if not directly internet-facing, attackers on the same network segment could exploit it)
  4. Check if remote management features are enabled
    Review device configuration for enabled management protocols (HTTP, HTTPS, SSH, Telnet) and their accessibility. In the web UI, check System > Management or similar. Via CLI, use 'show configuration' to review management settings.
    Affected if Remote management interfaces are accessible from non-trusted network segments (the vulnerability is exploitable via network-adjacent access to these interfaces)

You are affected if you have an EdgeMAX EdgeSwitch running firmware version 1.11.0 or earlier with its management interface accessible from the network.

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 EdgeMAX EdgeSwitch firmware to version 1.11.1 or later to address the improper input validation vulnerability. Organizations should identify affected devices in their network and schedule firmware updates following vendor release notes and best practices for network device patching.

Recommended fix High confidence

Version 1.11.1 or later

  1. 1. Identify the current EdgeMAX EdgeSwitch firmware version running on the device
  2. 2. Navigate to the official Ubiquiti downloads or support portal to obtain firmware version 1.11.1 or later
  3. 3. Review release notes for any prerequisites or注意事项 before upgrading
  4. 4. Back up the current device configuration as a precautionary measure
  5. 5. Upload and apply the firmware update through the EdgeSwitch management interface
  6. 6. Verify the upgrade was successful by confirming the new firmware version

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-48978 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