CVE-2025-26056
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 · uneditedA command injection vulnerability exists in the Infinxt iEdge 100 2.1.32 in the Troubleshoot module "MTR" functionality. The vulnerability is due to improper validation of user-supplied input in the mtrIp parameter. An attacker can exploit this flaw to execute arbitrary operating system commands on the underlying system with the same privileges as the web application process.
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 confidenceInfinxt iEdge 100 version 2.1.32 contains a command injection vulnerability in the Troubleshoot module's MTR (traceroute) functionality. The mtrIp parameter accepts user input that is passed to the underlying operating system without proper sanitization, allowing an attacker to inject shell commands. The commands execute with the privileges of the web application process.
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 installed iEdge 100 versionAccess the web management interface and navigate to System > About or Settings > Version. Alternatively, log into the CLI and run 'show version' or 'system info' command.Affected if The displayed version is exactly 2.1.32.
-
Confirm the Troubleshoot module is enabledIn the web interface, locate the Troubleshoot or Diagnostics module in the navigation menu. Check if the module is visible and accessible to users.Affected if The Troubleshoot module is present and enabled in the interface.
-
Verify MTR functionality is accessibleIn the Troubleshoot module, look for MTR (traceroute) or network diagnostics features. Attempt to access or view the MTR configuration page.Affected if MTR/traceroute functionality exists and can be accessed (even if not actively used).
-
Check if mtrIp parameter accepts inputInspect the HTTP requests when using the MTR feature via browser developer tools or proxy. Look for a parameter named 'mtrIp' in POST/GET requests sent to the device.Affected if The mtrIp parameter is present and accepts user-supplied values without apparent validation.
You are affected if you are running Infinxt iEdge 100 version 2.1.32 and the Troubleshoot module with MTR functionality is enabled and accessible.
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 dataImplement strict input validation on the mtrIp parameter, specifically validating that the input conforms to a valid IP address or hostname format using allowlist validation, and sanitize or reject any shell metacharacters before passing the input to system calls.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26056 — 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-26056 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