dbcve.org
Path TraversalWeakness · CWE-22

CVE-2025-8749

MEDIUM · 6.5 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 →
71/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
Path Traversal vulnerability in API Endpoint in Mobile Industrial Robots (MiR) Software Versions prior to 3.0.0 on MiR Robots allows authenticated users to extract files from the robot file system via a crafted API request.

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 path traversal vulnerability exists in the API endpoint of MiR Robots software versions prior to 3.0.0. Authenticated users can craft malicious API requests containing directory traversal sequences (e.g., ../../) to access and extract arbitrary files from the robot's file system outside the intended directory boundaries.

MitigationUpgrade MiR Robot software to version 3.0.0 or later, which contains the patch for this vulnerability. If immediate upgrade is not feasible, implement strict input validation on API endpoints to reject requests containing path traversal sequences and restrict API access to only necessary personnel.

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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 MiR Robots software installation
    Locate and confirm MiR Robots software on your system. Check for MiR-related processes, services, or installation directories. Look for MiR configuration files or the MiR web interface typically accessible on port 8080 or 443.
    Affected if MiR Robots software is installed and running on the system
  2. Determine installed software version
    Access the MiR web interface or API documentation to find the software version. Typically found in the system settings, about page, or by querying the API endpoint (e.g., GET /api/version or /api/system/info). Compare the version number to 3.0.0.
    Affected if The installed version is prior to 3.0.0 (e.g., 2.x.x or lower)
  3. Verify API endpoint accessibility
    Confirm that the MiR API endpoint is accessible from your network. Check if the API port (commonly 8080, 8443, or 443) is open and responding. Attempt to reach a known API endpoint to verify the service is running.
    Affected if The API endpoint is exposed and accepts connections from your location
  4. Confirm API authentication status
    Determine if API access requires authentication. Check whether valid credentials are configured and whether the API enforces authentication for path traversal-vulnerable endpoints.
    Affected if Authenticated users can access the API endpoints

Your environment is affected if MiR Robots software is installed with a version prior to 3.0.0 and the API endpoint is 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 Robot software to version 3.0.0 or later, which contains the patch for this vulnerability. If immediate upgrade is not feasible, implement strict input validation on API endpoints to reject requests containing path traversal sequences and restrict API access to only necessary personnel.

Recommended fix High confidence

MiR Software version 3.0.0

  1. Verify current MiR Robot software version via the web interface or API
  2. Download MiR Software version 3.0.0 or later from the official support portal at supportportal.mobile-industrial-robots.com
  3. Review release notes for version 3.0.0 to understand any configuration or operational changes
  4. Create a backup of current robot configuration and any custom settings
  5. Schedule maintenance window as the update may require robot downtime
  6. Upload the software package through the MiR web interface or API according to official documentation
  7. Verify the upgrade completed successfully by checking the software version
  8. Test that the path traversal vulnerability is remediated by attempting a benign, authorized API request that would have previously been vulnerable
Caveat Review release notes for version 3.0.0 - some API endpoints or configuration formats may have changed

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 / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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 locally
dbcve dependency scanner

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