CVE-2025-41735
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 upload any file to an arbitrary location due to missing file check resulting in remote code execution.
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 confidenceA file upload vulnerability exists where low-privileged authenticated users can upload files to arbitrary locations on the server due to missing file validation and path checks. This allows placing executable files in web-accessible directories, leading to remote code execution.
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< 2.2.0< 2.2.0< 2.2.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 the Metz Connect Ewio2 device modelLocate the device physically or check the web interface for the model identifier - look for Ewio2 M, Ewio2 M Bm, or Ewio2 Bm labelingAffected if The device is one of these three models and is accessible on the network
-
Determine the installed firmware versionAccess the device web interface, typically at the device IP address, and navigate to System > Firmware, Status, or About page. Alternatively, check via API endpoint or SNMP if availableAffected if The firmware version displayed is below 2.2.0 (for example, 2.1.x, 2.0.x, or earlier)
-
Verify the file upload feature is accessibleCheck if the web interface contains file upload functionality - look for firmware update, configuration import, data upload, or similar features in the admin panelAffected if File upload functionality is present and accessible to the authenticated user (even low-privileged accounts)
-
Confirm upload directory is web-accessibleIf file upload is possible, attempt to upload a test file and determine its storage path by accessing it via HTTP/HTTPS, or review any documentation/configuration that specifies upload storage pathsAffected if Uploaded files are stored in web-accessible directories (such as /www, /web, /html, or similar web root paths)
You are affected if you have a Metz Connect Ewio2, Ewio2 M Bm, or Ewio2 Bm device running firmware version below 2.2.0 with the file upload feature enabled and accessible.
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 · scoped2.2.0
Implement proper file validation including file type/mime type verification, filename sanitization, path traversal prevention, restrict upload directories to non-executable locations, and enforce strict access controls on upload functionality.
Ewio2 M / Ewio2 M Bm / Ewio2 Bm Firmware version 2.2.0
- Identify all Ewio2 M, Ewio2 M Bm, and Ewio2 Bm devices in the environment running firmware versions prior to 2.2.0
- Obtain the firmware version 2.2.0 or later from the official Ewio vendor (certvde.com or vendor website)
- Review the vendor's firmware update documentation for the correct upgrade procedure
- Apply the firmware upgrade to each affected device, ensuring the upgrade completes successfully
- Verify that the upgraded devices are running version 2.2.0 or later after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.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 $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41735 — 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-41735 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