Unauthenticated file writes via unchecked ZIP paths
Published May 31, 2022 · Updated Jul 9, 2026
Path traversal in Webbank WeCube 3.2.2 allows remote attackers to write outside the extraction directory via a crafted ZIP file. The unzipLocalFile method concatenates each ZipEntry name directly with the destination path without rejecting ../ segments or verifying the canonical path. No authentication or user interaction is required, and exploitation creates or appends data to files writable by the WeCube process.
Summary
What happened
Path traversal in Webbank WeCube 3.2.2 allows remote attackers to write outside the extraction directory via a crafted ZIP file. The unzipLocalFile method concatenates each ZipEntry name directly with the destination path without rejecting ../ segments or verifying the canonical path. No authentication or user interaction is required, and exploitation creates or appends data to files writable by the WeCube process.
The record
- CVE
- CVE-2022-28945
- Published
- May 31, 2022
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- May 31, 2022CVE publishedPublication date reported by the CVE source.
- Jul 9, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- zip-slip issue demonstrationproof of concept · unverified
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo