Authenticated dangerous-file upload via unchecked image extension
Published May 20, 2020 · Updated Aug 4, 2024
Unrestricted file upload in Microweber 1.1.18 allows local users to place dangerous files through the Edit User image control. The users edit route accepts the Add Image filename without verifying that its extension belongs to an image type, so a disguised PHP web shell passes the upload control. An authenticated Microweber session and access to the Edit User screen are required; a successful upload can place a web shell on the server and grant file-system access.
Summary
What happened
Unrestricted file upload in Microweber 1.1.18 allows local users to place dangerous files through the Edit User image control. The users edit route accepts the Add Image filename without verifying that its extension belongs to an image type, so a disguised PHP web shell passes the upload control. An authenticated Microweber session and access to the Edit User screen are required; a successful upload can place a web shell on the server and grant file-system access.
The record
- CVE
- CVE-2020-13241
- Published
- May 20, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-434, T1505.003
- Attack vector
- local
- Privileges
- authenticated
Timeline
How it unfolded
- May 20, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Microweber File upload vulnerability proof of conceptfunctional · 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