Advanced uploader <= 4.2 - Authenticated (Subscriber+) Arbitrary File Upload
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Advanced uploader
- Affected Version
<= 4.2- CVSS
- 5.4Medium
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2022-1103
At a glance
CVE-2022-1103 is a medium-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Advanced uploader WordPress plugin, affecting versions <= 4.2. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Subscriber level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed April 2022, reported by Roel van Beurden.
Vulnerability Overview
The Advanced uploader WordPress plugin through 4.2 allows any authenticated users like subscriber to upload arbitrary files, such as PHP, which could lead to Remote Code Execution
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 interaction from a victim user.
CWE-434: Unrestricted Upload of File with Dangerous Type
Reaching this weakness in Advanced uploader <= 4.2 takes an account at Subscriber level or above. 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. No fixed build of this plugin is recorded for Advanced uploader yet, so installs running <= 4.2 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: 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. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C