dbcve.org
Universal Bacnet Router FirmwareOperating system · Mbs Solutions

CVE-2025-41757

HIGH · 8.8 CVSS v3.1 Published 2026-03-09
Fix available
A fix is available. Upgrade to 6.0.1.0 or later.
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
A low-privileged remote attacker can abuse the backup restore functionality of UBR (ubr-restore) which runs with elevated privileges and does not validate the contents of the backup archive to create or overwrite arbitrary files anywhere on the 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 · high confidence

A path traversal vulnerability exists in UBR's backup restore functionality (ubr-restore). The service runs with elevated privileges but fails to validate or sanitize the contents of backup archives, allowing a low-privileged remote attacker to craft malicious archives containing path traversal sequences (e.g., ../../etc/passwd) to write or overwrite arbitrary files anywhere on the filesystem, enabling privilege escalation to root.

MitigationImplement strict validation of archive contents including path sanitization to prevent traversal sequences, run the restore process with least privilege, and validate file write locations against an allowlist of permitted paths.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Universal Bacnet Router FirmwareOperating system
Affected:< 6.0.1.0

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 the firmware version
    Access the Universal Bacnet Router web interface or CLI and locate the firmware version information, typically found in System > About, Status, or a similar administration section
    Affected if The installed firmware version is below 6.0.1.0
  2. Verify the ubr-restore binary exists
    Check for the presence of the ubr-restore executable on the device filesystem, typically located in /usr/sbin/, /sbin/, or the vendor's bin directory
    Affected if The ubr-restore binary is present on the system
  3. Confirm the backup restore service is enabled
    Examine the router's configuration settings, web interface, or startup scripts to determine if the backup restore functionality is actively enabled or exposed
    Affected if Backup restore is enabled or accessible as a feature
  4. Verify service privilege level
    Check the process information, service configuration, or init scripts to determine what user/context the ubr-restore service executes under
    Affected if The service runs with root or elevated system privileges
  5. Check restore function accessibility
    Determine if the backup restore endpoint/interface is accessible to low-privileged or remote users without additional authentication barriers
    Affected if The restore function can be invoked by low-privileged or remote attackers

The environment is affected if the firmware version is below 6.0.1.0, the ubr-restore service is enabled, and it runs with elevated privileges while accepting unvalidated archive contents from accessible restore interfaces.

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
Upgrade available Upgrade to 6.0.1.0 or later
Fixed in 6.0.1.0
Interim mitigation

Implement strict validation of archive contents including path sanitization to prevent traversal sequences, run the restore process with least privilege, and validate file write locations against an allowlist of permitted paths.

Recommended fix Moderate confidence

Universal Bacnet Router Firmware version 6.0.1.0 or later

  1. 1. Identify all Universal Bacnet Router (UBR) devices in your inventory
  2. 2. Check the current firmware version on each device through the administrative interface or CLI
  3. 3. Download the firmware version 6.0.1.0 or later from the official vendor source (www.mbs-solutions.de)
  4. 4. Follow the vendor's documented firmware upgrade procedure for UBR devices
  5. 5. After upgrading, verify the firmware version has been successfully updated to 6.0.1.0 or later
  6. 6. Test the backup restore functionality to confirm it works correctly with the new version
  7. 7. Consider implementing additional access controls to limit who can access the backup restore functionality until the upgrade is complete

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

Fix this in Universal Bacnet Router Firmware Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing10.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,580
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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