CVE-2025-63371
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 · uneditedMilos Paripovic OneCommander 3.102.0.0 is vulnerable to Directory Traversal. The vulnerability resides in the ZIP file processing component, specifically in the functionality responsible for extracting and handling ZIP archive contents.
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 confidenceOneCommander 3.102.0.0 contains a directory traversal vulnerability in its ZIP file extraction component. By crafting a malicious ZIP archive containing path traversal sequences (e.g., '../') in filenames, an attacker can cause the application to write files to arbitrary locations outside the intended extraction directory, potentially achieving remote code execution or 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= 3.102.0.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
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/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.
-
Confirm OneCommander installationCheck for OneCommander installation by looking for the executable (OneCommander.exe) in typical locations: %ProgramFiles%\OneCommander, %LocalAppData%\Programs\OneCommander, or search for the file using Get-ChildItem -Path $env:ProgramFiles -Recurse -Filter 'OneCommander.exe' -ErrorAction SilentlyContinueAffected if OneCommander.exe is found on the system
-
Identify installed versionRight-click the OneCommander.exe file, select Properties, then view the Details tab to see the File Version. Alternatively, run the application and check Help > About, or use: (Get-Item 'C:\Program Files\OneCommander\OneCommander.exe').VersionInfo.FileVersionAffected if The version is exactly 3.102.0.0
-
Verify ZIP extraction usageOneCommander includes a built-in ZIP extraction feature accessible by opening a ZIP file and clicking Extract, or by right-clicking a ZIP archive. Check if the user has used this feature by examining recent extraction operations in the application's activity history or file system.Affected if The ZIP extraction feature has been used to extract archives from untrusted sources
A system is affected only if OneCommander version 3.102.0.0 is installed and has been used to extract ZIP files from untrusted or unknown sources.
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.
From vendor dataUpdate to a patched version of OneCommander once available. Until then, avoid extracting untrusted ZIP files with OneCommander and consider using alternative archive utilities with stricter path validation.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-63371 — 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-63371 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