CVE-2025-41736
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 a new or overwrite an existing python script by using a path traversal of the target filename in php resulting in a 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 path traversal vulnerability in PHP file upload functionality allows low-privileged remote attackers to specify a directory traversal path for the target filename, enabling them to upload new or overwrite existing Python scripts on the server, which then execute 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 firmware versionAccess the device administrative interface or check /etc/version, /proc/version, or the system info page to determine the installed firmware version of the Metz Connect Ewio2, Ewio2 M, or Ewio2 M Bm deviceAffected if The firmware version is below 2.2.0 (e.g., 2.1.x, 2.0.x, or earlier)
-
Locate the PHP upload configurationInspect the PHP configuration file (typically php.ini) or the web server configuration for the file upload settings; look for the 'file_uploads' directive and 'upload_tmp_dir' pathAffected if PHP file uploads are enabled (file_uploads=On) and the upload temporary directory is within the web root
-
Verify the upload directory locationCheck the application's configuration or source code to determine where uploaded files are stored; inspect the web server document root and the upload path configurationAffected if Uploaded files are stored inside the web-accessible directory (document root) rather than outside of it
-
Check script execution policy in upload directoriesInspect the web server configuration (e.g., Apache .htaccess, nginx config) for the upload directory; look for handlers that allow execution of Python or script file typesAffected if Script execution is permitted in the upload directory (no restrictions on .py, .php, or other executable file types)
-
Inspect the file upload handler for path validationExamine the PHP code handling file uploads (if accessible via web shell or firmware extraction); look for path traversal vulnerability in the filename parameter handlingAffected if The upload handler does not properly sanitize the destination filename and allows '..' sequences or absolute paths
A user is affected if the device runs firmware version below 2.2.0 and the PHP file upload functionality is enabled with uploads stored in a web-accessible location where script execution is not blocked.
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 strict input validation on file upload paths using basename() to strip traversal sequences, store uploads outside the web root, enforce an allowlist of permitted file extensions, and disable script execution in upload directories.
2.2.0 (for Ewio2 M Firmware, Ewio2 M Bm Firmware, and Ewio2 Bm Firmware)
- 1. Obtain the firmware version 2.2.0 or later from the vendor (certvde.com or Ewio2 manufacturer)
- 2. Access the Ewio2 device administration interface
- 3. Navigate to the firmware update or system settings section
- 4. Upload and apply the firmware version 2.2.0 or later
- 5. Verify the upgrade was successful by checking the firmware version in the device settings
- 6. Confirm that the device is functioning normally after the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation12.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 $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41736 — 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-41736 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