Unauthenticated code execution via file-type modification
Published Dec 20, 2022 · Updated Apr 17, 2025
Unrestricted file upload in WBCE CMS 1.5.4 allows remote attackers to execute server-side code by changing an upload file type. The public record does not identify the upload handler or disclose how its file-type validation accepts a dangerous server-executable file. No authentication is required according to the published CVSS assessment, and successful exploitation executes code in the web server context.
Summary
What happened
Unrestricted file upload in WBCE CMS 1.5.4 allows remote attackers to execute server-side code by changing an upload file type. The public record does not identify the upload handler or disclose how its file-type validation accepts a dangerous server-executable file. No authentication is required according to the published CVSS assessment, and successful exploitation executes code in the web server context.
The record
- CVE
- CVE-2022-46020
- Published
- Dec 20, 2022
- Updated
- Apr 17, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, T1190
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Dec 20, 2022CVE publishedPublication date reported by the CVE source.
- Apr 17, 2025Record 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
- WBCE CMS 1.5.4 getshell proof documentproof 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