CVE-2025-52377
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 · uneditedCommand injection vulnerability in Nexxt Solutions NCM-X1800 Mesh Router versions UV1.2.7 and below, allowing authenticated attackers to execute arbitrary commands on the device. The vulnerability is present in the web management interface's ping and traceroute functionality, specifically in the /web/um_ping_set.cgi endpoint. The application fails to properly sanitize user input in the `Ping_host_text` parameter before passing it to the underlying system command, allowing attackers to inject and execute arbitrary shell commands as the root user.
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 confidenceCommand injection vulnerability in Nexxt Solutions NCM-X1800 Mesh Router firmware UV1.2.7 and below. The /web/um_ping_set.cgi endpoint fails to sanitize the Ping_host_text parameter before passing it to system commands, allowing authenticated attackers to inject and execute arbitrary shell commands as root.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLocate the device label or check the web interface header for the model name NCM-X1800Affected if The device is not a Nexxt Solutions NCM-X1800 Mesh Router (different models are not affected by this specific CVE)
-
Check the installed firmware versionAccess the router web interface, navigate to the firmware or system settings page, and note the firmware version displayed (typically labeled as firmware version, software version, or UV version)Affected if The firmware version is UV1.2.7 or any version numbered lower than UV1.2.7 (versions above UV1.2.7 are not affected)
-
Verify web management interface accessibilityAttempt to access the router web interface at the default IP (commonly 192.168.1.1 or 192.168.0.1) in a web browserAffected if The web management interface is exposed and accessible (the vulnerability requires authenticated access to /web/um_ping_set.cgi)
-
Confirm Ping_host_text parameter exposureIf authenticated access is available, examine the ping functionality in the web interface or attempt a request to /web/um_ping_set.cgi to verify the endpoint exists and accepts the Ping_host_text parameterAffected if The /web/um_ping_set.cgi endpoint exists and accepts the Ping_host_text parameter without sanitization (the command injection occurs through this parameter)
You are affected if you are running a Nexxt Solutions NCM-X1800 Mesh Router with firmware UV1.2.7 or below, and the web management interface is accessible (since the attacker needs authentication to reach the vulnerable /web/um_ping_set.cgi endpoint).
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataApply vendor firmware update when available. Until then, restrict access to the web management interface to trusted users only, as the ping/traceroute functionality lacks proper input validation allowing arbitrary command execution.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-52377 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-52377 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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