Authenticated code execution via unrestricted Elfinder upload
Published Dec 10, 2025 · Updated Dec 10, 2025
Unrestricted PHP upload in WBCE CMS 1.6.2 allows remote authenticated users to execute arbitrary commands through Elfinder. The connector.wbce.php upload handler accepts an upload[] file named shell.inc and stores it under /media without blocking executable PHP content. Backend credentials are required; a planted web shell then runs cmd input in the web-server process context.
Summary
What happened
Unrestricted PHP upload in WBCE CMS 1.6.2 allows remote authenticated users to execute arbitrary commands through Elfinder. The connector.wbce.php upload handler accepts an upload[] file named shell.inc and stores it under /media without blocking executable PHP content. Backend credentials are required; a planted web shell then runs cmd input in the web-server process context.
The record
- CVE
- CVE-2024-58283
- Published
- Dec 10, 2025
- Updated
- Dec 10, 2025
- Vendor
- WBCE Project
- Product
- WBCE CMS
- Classifications
- CWE-434, T1505.003
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 10, 2025CVE publishedPublication date reported by the CVE source.
- Dec 10, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=1.6.2
What conditions does exploitation require?
What is affected?
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 v1.6.2 Remote Code Executionfunctional · demonstrated
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