dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-52379

MEDIUM · 5.4 CVSS v3.1 Published 2025-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
60/100
Remediation priority · Elevated
Remotely reachable 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
Nexxt Solutions NCM-X1800 Mesh Router firmware UV1.2.7 and below contains an authenticated command injection vulnerability in the firmware update feature. The /web/um_fileName_set.cgi and /web/um_web_upgrade.cgi endpoints fail to properly sanitize the upgradeFileName parameter, allowing authenticated attackers to execute arbitrary OS commands on the device, resulting in remote code execution.

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

Authenticated command injection vulnerability in Nexxt Solutions NCM-X1800 Mesh Router firmware (UV1.2.7 and below). The /web/um_fileName_set.cgi and /web/um_web_upgrade.cgi endpoints fail to sanitize the upgradeFileName parameter, allowing authenticated attackers to inject and execute arbitrary OS commands via the firmware update feature.

MitigationUpdate to a patched firmware version above UV1.2.7 when available. Until then, restrict administrative web interface access to trusted networks/users and monitor for unauthorized access.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

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. Identify the device model
    Access the router web interface or check the device label to confirm the model is NCM-X1800 Mesh Router from Nexxt Solutions
    Affected if The device is not a Nexxt Solutions NCM-X1800 Mesh Router
  2. Check installed firmware version
    Log into the router administrative web interface and navigate to the firmware/version information page, or use the command interface to retrieve the firmware version string
    Affected if The firmware version is UV1.2.7 or lower (any version at or below UV1.2.7)
  3. Verify web interface accessibility
    Attempt to reach the router web administration interface over HTTP/HTTPS from a network-connected host
    Affected if The administrative web interface is exposed and reachable
  4. Confirm firmware update feature availability
    In the web interface, locate the firmware upgrade or update section (typically under Administration, Maintenance, or System settings)
    Affected if The firmware update functionality is present and configurable
  5. Check authentication status
    Determine whether valid administrator credentials for the router are known or potentially compromised
    Affected if Attacker has valid admin credentials to access the firmware update endpoints

A user is affected if they have a Nexxt Solutions NCM-X1800 Mesh Router running firmware version UV1.2.7 or below with an accessible administrative web interface where the firmware update feature can be accessed by an authenticated attacker.

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 to a patched firmware version above UV1.2.7 when available. Until then, restrict administrative web interface access to trusted networks/users and monitor for unauthorized access.

Recommended fix Moderate confidence

Firmware version above UV1.2.7 (contact Nexxt Solutions for the exact fixed release)

  1. 1. Identify the current firmware version of the Nexxt Solutions NCM-X1800 Mesh Router by accessing the admin web interface or checking via CLI
  2. 2. Navigate to the firmware update or administration section of the router's web interface
  3. 3. Download the firmware update from the official Nexxt Solutions support website or vendor repository
  4. 4. Upload and apply the firmware update that addresses the command injection vulnerability in the um_fileName_set.cgi and um_web_upgrade.cgi endpoints
  5. 5. After the update completes, verify the new firmware version is above UV1.2.7
  6. 6. Confirm the upgradeFileName parameter is now properly sanitized by testing the affected endpoints with the same input that previously triggered the vulnerability
Caveat Review release notes for any configuration or feature changes between versions; backup router configuration before upgrading

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

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA6.0 h
34.0 hours of engineering $5,940
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-52379 — 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-52379 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