WPtouch <= 3.4.2 - Arbitrary File Upload
Strategic Overview
- Status
- Patched in 3.4.3
- Affected Plugin
- WPtouch – Make your WordPress Website Mobile-Friendly
- Affected Version
<= 3.4.2- CVSS
- 9.9Critical
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE pending
At a glance
This record tracks a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the WPtouch WordPress plugin, affecting versions <= 3.4.2. It carries a CVSS score of 9.9 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 3.4.3; sites on affected versions should update now. Disclosed August 2014, reported by Marc-Alexandre Montpas.
Vulnerability Overview
The WPtouch plugin for WordPress is vulnerable to arbitrary file upload in versions up to, and including, 3.4.2. This is due to the 'admin_initialize()' method being called by the 'admin_init' hook and a lack of capability checks on the function. This makes it possible for authenticated attackers to upload a backdoor, they can then use it to take complete control of the website.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-434: Unrestricted Upload of File with Dangerous Type
WPtouch <= 3.4.2 carries this weakness at admin_init, and reaching it takes a caller who can reach the endpoint. 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 WPtouch the fix is 3.4.3: builds <= 3.4.2 are affected, anything from 3.4.3 onward is not.
Remediation
Update to version 3.4.3, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WPtouch: 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: WPtouch 3.4.3 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WPtouch – Make your WordPress Website Mobile-Friendly
- 7.3CVE-2011-4803: WPtouch <= 1.9.8 SQL Injection
CVE-2011-4803 - 7.2CVE-2022-3417: WPtouch <= 4.3.44 PHP Object Injection
CVE-2022-3417 - 7.2WPtouch <= 3.7.5.3 Cross-Site Scripting
- 6.1WPtouch <= 4.3.42 Reflected Cross-Site Scripting
- 6.1WPtouch < 1.9.30 Open Redirect
- 6.1CVE-2010-4779: WPtouch < 1.9.20 Cross-Site Scripting
CVE-2010-4779 - 4.4CVE-2025-49318: WPtouch <= 4.3.60 Stored Cross-Site Scripting
CVE-2025-49318 - 4.3WPTouch < 3.7 Open Redirect
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C