WP ULike Pro <= 1.9.3 - Unauthenticated Limited Arbitrary File Upload
Strategic Overview
- Status
- Patched in 1.9.4
- Affected Plugin
- WP ULike Pro
- Affected Version
<= 1.9.3- CVSS
- 6.1Medium
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2024-9648
At a glance
CVE-2024-9648 is a medium-severity Unrestricted Upload of File with Dangerous Type vulnerability in the WP ULike Pro WordPress plugin, affecting versions <= 1.9.3. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.9.4; sites on affected versions should update now. Disclosed August 2025, reported by wesley (wcraft).
Vulnerability Overview
The WP ULike Pro plugin for WordPress is vulnerable to arbitrary file uploads due to insufficient file type validation in the WP_Ulike_Pro_File_Uploader class in all versions up to, and including, 1.9.3. This makes it possible for unauthenticated attackers to upload limited arbitrary files like .php2, .php6, .php7, .phps, .pht, .phtm, .pgif, .shtml, .phar, .inc, .hphp, .ctp, .module, .html, .svg on the affected site's server which may make make other attacks like Cross-Site Scripting possible. Only versions up to 1.8.7 were confirmed vulnerable, however, the earliest tested version for a patch we have access to is 1.9.4, so we are considering 1.9.4 the patched version.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-434: Unrestricted Upload of File with Dangerous Type
Reaching this weakness in WP ULike Pro <= 1.9.3 takes no account at all. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.
If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For WP ULike Pro the fix is 1.9.4: builds <= 1.9.3 are affected, anything from 1.9.4 onward is not.
Remediation
Update to version 1.9.4, or a newer patched version
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WP ULike Pro 1.9.4 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Login Security
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C