dbcve.org
Universal Bacnet Router FirmwareOperating system · Mbs Solutions

CVE-2025-41764

CRITICAL · 9.1 CVSS v3.1 Published 2026-03-09
Fix available
A fix is available. Upgrade to 6.0.1.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 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
Due to insufficient authorization enforcement, an unauthorized remote attacker can exploit the wwwupdate.cgi endpoint to upload and apply arbitrary updates.

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

The wwwupdate.cgi endpoint lacks proper authorization checks, allowing any remote attacker to upload and apply arbitrary system updates. This enables complete system compromise through the update mechanism without requiring authentication.

MitigationImplement robust authorization enforcement on wwwupdate.cgi to verify user privileges before permitting upload and apply operations. Consider additional integrity verification of update packages.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 device model
    Access the device web interface or use SNMP/SSH to retrieve the device model information. Look for 'Mbs Solutions Universal Bacnet Router' or check the device identifier in the administrative console.
    Affected if The device is an Mbs Solutions Universal Bacnet Router
  2. Determine the installed firmware version
    Navigate to the device administrative panel, typically under System > Info, Status, or About page. Alternatively, access the device via SSH and run commands such as 'show version', 'cat /proc/version', or check /etc/version if accessible via the firmware.
    Affected if Firmware version is displayed as less than 6.0.1.0
  3. Verify wwwupdate.cgi endpoint accessibility
    Attempt to access the URL path /cgi-bin/wwwupdate.cgi or /wwwupdate.cgi on the device's web server using a browser or HTTP client (e.g., curl http://<device-ip>/cgi-bin/wwwupdate.cgi).
    Affected if The endpoint returns a response rather than a 404 or 403 error, indicating it exists and may be accessible
  4. Check web service configuration for wwwupdate.cgi
    Inspect the web server configuration files (e.g., httpd.conf, lighttpd.conf, or equivalent) if accessible via firmware extraction or administrative console. Look for handlers or aliases mapping wwwupdate.cgi.
    Affected if wwwupdate.cgi is registered as an active CGI handler without explicit access restrictions

The device is affected if it is an Mbs Solutions Universal Bacnet Router running firmware version prior to 6.0.1.0 AND the wwwupdate.cgi endpoint is accessible without authentication.

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 robust authorization enforcement on wwwupdate.cgi to verify user privileges before permitting upload and apply operations. Consider additional integrity verification of update packages.

Recommended fix Moderate confidence

Universal Bacnet Router Firmware 6.0.1.0 or later

  1. Verify current firmware version on the Universal Bacnet Router device
  2. Download the firmware version 6.0.1.0 or later from the official vendor source (www.mbs-solutions.de)
  3. Access the router's administrative interface using authenticated credentials
  4. Navigate to the firmware update section
  5. Upload and apply the downloaded firmware (6.0.1.0 or later)
  6. Verify the update was successful by checking the new firmware version
  7. Confirm the wwwupdate.cgi endpoint now requires proper authorization

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

Fix this in Universal Bacnet Router Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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