CVE-2025-41762
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 · uneditedAn unauthenticated attacker can abuse the weak hash of the backup generated by the wwwdnload.cgi endpoint to gain unauthorized access to sensitive data, including password hashes and certificates.
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 confidenceThe wwwdnload.cgi endpoint generates backups protected by a weak hash algorithm, allowing unauthenticated attackers to forge or crack the hash and download sensitive backup files containing password hashes and certificates.
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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify device model and firmware versionAccess the device admin interface or check the system information page to determine the exact firmware version of the Mbs Solutions Universal Bacnet RouterAffected if Firmware version is below 6.0.1.0
-
Locate the wwwdnload.cgi endpointCheck if the /wwwdnload.cgi endpoint is accessible on the device by attempting to access it via HTTP/HTTPSAffected if The endpoint exists and responds to requests
-
Test backup file download capabilityAttempt to download a backup file through the wwwdnload.cgi endpoint without authenticationAffected if Backup files can be downloaded without authentication or valid credentials
-
Inspect downloaded backup file contentsExtract and examine the downloaded backup file for sensitive data such as password hashes and certificatesAffected if Backup file contains plaintext or weakly protected password hashes and certificates
The device is affected if it runs Mbs Solutions Universal Bacnet Router firmware below version 6.0.1.0 and the wwwdnload.cgi endpoint allows unauthenticated access to backup files containing sensitive credentials.
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
Replace the weak hash with a strong, modern algorithm (e.g., Argon2, bcrypt, or PBKDF2) and enforce proper authentication and authorization on the backup download endpoint.
Firmware version 6.0.1.0
- Obtain firmware version 6.0.1.0 or later from the official vendor (www.mbs-solutions.de)
- Access the Universal Bacnet Router administrative interface via web browser
- Navigate to the firmware update or system upgrade section in the management console
- Upload the firmware file (6.0.1.0 or later) and initiate the upgrade process
- Wait for the firmware to be applied and the device to reboot
- Verify the firmware version has been updated to 6.0.1.0 or later in the router's interface
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.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,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41762 — 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-41762 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