CVE-2018-0646
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 · uneditedDirectory traversal vulnerability in Explzh v.7.58 and earlier allows an attacker to read arbitrary files via unspecified vectors.
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 confidenceExplzh versions 7.58 and earlier contain a directory traversal vulnerability that allows authenticated or unauthenticated attackers to escape the intended directory boundaries and read arbitrary files on the host system via unspecified vectors. This is a path traversal issue likely exploitable through archive extraction functionality, enabling unauthorized file system access with information disclosure impact.
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<= 7.58CVSS 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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 installed Explzh versionOpen Explzh and access the Help > About menu, or right-click the executable file and view its Properties to see the version number. Alternatively, locate the Explzh executable (explzh.exe) in the program directory and check its file properties.Affected if The version displayed is 7.58 or any version lower than 7.59
-
Confirm the product is Ponsoftware ExplzhVerify that the archive utility software is specifically Ponsoftware Explzh and not another archive tool, as this CVE applies only to Explzh.Affected if The software is Ponsoftware Explzh and the version is 7.58 or earlier
-
Check for the vulnerable archive extraction featureThe vulnerability is exploitable through archive extraction functionality. Identify whether users have the ability to extract or open archive files (ZIP, 7z, CAB, ARJ, RAR, etc.) using Explzh.Affected if The archive extraction feature is available and users can open or extract archive files
-
Review for signs of unauthorized file accessCheck system logs, application logs, and file system audit logs for any unusual read operations on files outside the intended extraction directory. Look for access patterns where files were read from system directories (Windows, System32, Program Files) or user-specified paths that differ from the extraction destination.Affected if Logs show file read operations from arbitrary system locations that were not intentionally accessed by the user
A user is affected if they are running Explzh version 7.58 or earlier and the archive extraction feature is in use, since the path traversal flaw allows escaping the intended directory during extraction.
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 dataUpgrade to Explzh version 7.59 or later to obtain the vendor patch. Additionally, restrict file access permissions and monitor for unusual file access patterns from systems running the affected software.
- Consultation2.0 h
- Implementation1.0 h
- Testing1.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 $1,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-0646 — 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-2018-0646 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