CVE-2025-41765
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 · uneditedDue to insufficient authorization enforcement, an unauthorized remote attacker can exploit the wwwupload.cgi endpoint to upload and apply arbitrary data. This includes, but is not limited to, contact images, HTTPS certificates, system backups for restoration, server peer configurations, and BACnet/SC server certificates and keys.
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 confidenceThe wwwupload.cgi web endpoint lacks proper authorization checks, allowing any remote attacker to upload arbitrary files including HTTPS certificates, system backups, peer configurations, and BACnet/SC server credentials. This enables full system compromise through restoreable backups, certificate hijacking for MITM attacks, and exposure of cryptographic keys.
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< 6.0.1.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify firmware versionAccess the router admin interface or check /proc/version, /etc/os-release, or the system's firmware information page to determine the installed MBS Solutions Universal Bacnet Router firmware versionAffected if The firmware version is less than 6.0.1.0
-
Locate wwwupload.cgi endpointCheck if the wwwupload.cgi file exists in the web server's CGI directory (commonly /cgi-bin/ or /www/cgi-bin/) by listing the directory contents or reviewing web server configuration filesAffected if The wwwupload.cgi script is present on the system
-
Verify endpoint accessibilityAttempt a GET request to the wwwupload.cgi endpoint from an unauthenticated context or examine web server access logs for unauthenticated requests to this endpointAffected if The endpoint responds without requiring authentication credentials
-
Inspect upload directoriesExamine directories where uploaded files are stored (typically /www/uploads/, /tmp/, or /var/www/uploads/) for unexpected files, particularly HTTPS certificates, backup files (.bak, .backup), peer configuration files, or BACnet/SC certificate/key filesAffected if Unknown or suspicious certificate files, backup files, or configuration files are present in upload directories that were not placed there by administrators
-
Review system certificate storesList and inspect certificate and key files in system directories (/etc/ssl/, /etc/bacnet/, or similar) for any certificates or keys that were not explicitly installed by the administratorAffected if Unexpected or unauthorized SSL certificates, private keys, or BACnet/SC credentials exist on the system
The system is affected if it runs MBS Solutions Universal Bacnet Router firmware below version 6.0.1.0 and the wwwupload.cgi endpoint is accessible without authentication, allowing potential file injection.
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.
dbcve · scoped6.0.1.0
Implement robust authentication and role-based authorization for all wwwupload.cgi operations. Restrict network access to trusted entities and validate all uploaded content before processing or applying changes.
6.0.1.0
- Access the Universal Bacnet Router administrative interface
- Navigate to the firmware upgrade section (typically under System > Firmware or Settings > Maintenance)
- Download the firmware version 6.0.1.0 or later from the official vendor source (www.mbs-solutions.de)
- Upload the firmware file to the device through the web interface or SCP/FTP if available
- Allow the firmware upload and installation process to complete - do not power off the device during this process
- After reboot, verify the firmware version shows 6.0.1.0 or later
- Confirm the wwwupload.cgi endpoint now properly enforces authorization
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41765 — 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-41765 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