CVE-2025-41758
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 · uneditedA low-privileged remote attacker can exploit an arbitrary file write vulnerability in the wwupload.cgi endpoint. Due to path traversal this can lead to overwriting arbitrary files on the device and achieving a full system compromise.
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 confidenceAn arbitrary file write vulnerability in the wwupload.cgi endpoint allows a low-privileged remote attacker to exploit path traversal and write files to arbitrary locations on the device, leading to full system compromise.
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
- 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 checksWork through these to decide whether this CVE applies to you.
-
Identify firmware versionAccess the device administrative interface or check the system information page to determine the installed firmware version of Mbs Solutions Universal Bacnet RouterAffected if The firmware version is lower than 6.0.1.0
-
Locate wwupload.cgi endpointAttempt to access the wwupload.cgi script via HTTP/HTTPS request (e.g., GET or POST to /cgi-bin/wwupload.cgi or similar path on the device's web interface)Affected if The wwupload.cgi endpoint is present and responds to requests, indicating the vulnerable component is enabled
-
Verify path traversal protectionReview the web server or application configuration files for the wwupload.cgi endpoint to determine if path traversal sanitization is implemented on file path parametersAffected if No input validation or path sanitization is configured for file upload parameters in wwupload.cgi
You are affected if the Mbs Solutions Universal Bacnet Router firmware version is below 6.0.1.0 and the wwupload.cgi endpoint is accessible without proper path traversal protection on file path parameters.
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 strict input validation and sanitization on file path parameters to prevent path traversal, restrict file write operations to designated safe directories, and apply vendor-supplied patches when available.
Universal Bacnet Router Firmware 6.0.1.0 or later
- Obtain the fixed firmware version 6.0.1.0 or later from the vendor (www.mbs-solutions.de)
- Review the vendor's firmware upgrade documentation for the Universal Bacnet Router
- Verify the integrity of the firmware file using checksums if provided by the vendor
- Access the device administration interface using authorized credentials
- Navigate to the firmware upgrade section of the web management interface
- Upload and apply the new firmware version 6.0.1.0
- Verify the upgrade was successful by checking the firmware version in the device interface
- Confirm that the wwupload.cgi endpoint is no longer vulnerable to path traversal
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41758 — 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-41758 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