dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-8748

HIGH · 8.8 CVSS v3.1 Published 2025-08-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
MiR software versions prior to version 3.0.0 are affected by a command injection vulnerability. A malicious HTTP request crafted by an authenticated user could allow the execution of arbitrary commands on the underlying operating system.

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 · moderate confidence

MiR software versions before 3.0.0 contain a command injection vulnerability where specially crafted HTTP requests from authenticated users can execute arbitrary operating system commands. The vulnerability stems from insufficient input validation in the HTTP request handling, allowing command separators or payload injection to reach the underlying system shell.

MitigationUpgrade MiR software to version 3.0.0 or later to remediate this vulnerability. Until the upgrade can be applied, implement network segmentation to limit access to the management interface and minimize the number of authenticated users.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify MiR software version
    Locate the MiR software installation and check its version number. This is typically found in the software's about panel, system information page, or by querying the management interface for version metadata.
    Affected if The installed version is any release before 3.0.0 (e.g., 2.x.x, 1.x.x)
  2. Verify HTTP management interface availability
    Confirm that the MiR management interface is accessible via HTTP/HTTPS. Check if the web service is running and reachable on the expected port.
    Affected if The HTTP management interface is enabled and reachable on the network
  3. Check authentication configuration
    Review the user authentication settings for the management interface to determine which users have access to HTTP request functionality.
    Affected if Any user account exists that can authenticate to the management interface, as the vulnerability requires authenticated access
  4. Inspect HTTP request handling configuration
    Examine the web server or application configuration files related to HTTP request processing. Look for settings that control input validation or command execution behavior.
    Affected if Input validation for HTTP request parameters is disabled or minimally configured

A user is affected if they are running any MiR software version before 3.0.0 with the HTTP management interface enabled and accessible to authenticated users.

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

Upgrade MiR software to version 3.0.0 or later to remediate this vulnerability. Until the upgrade can be applied, implement network segmentation to limit access to the management interface and minimize the number of authenticated users.

Recommended fix Moderate confidence

Version 3.0.0

  1. Identify the current MiR software version running on your robot by accessing the web interface or checking system information
  2. Access the MiR support portal at supportportal.mobile-industrial-robots.com or contact MiR support directly
  3. Download MiR software version 3.0.0 or later from the official support channels
  4. Follow MiR's documented upgrade procedure to apply the software update to your robot
  5. Verify the upgrade was successful and the software version shows 3.0.0 or later
  6. Confirm the command injection vulnerability is resolved by testing that arbitrary command execution is no longer possible

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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