Strategic Overview
- Status
- Patched in 0.1.14
- Affected Plugin
- Omni Secure Files
- Affected Version
<= 0.1.13- CVSS
- 9.8Critical
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2012-10064
At a glance
CVE-2012-10064 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Omni Secure Files WordPress plugin, affecting versions <= 0.1.13. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 0.1.14; sites on affected versions should update now. Disclosed June 2012, reported by Adrien Thierry.
Vulnerability Overview
The Omni Secure Files plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation via the upload.php file in versions up to, and including 0.1.13. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected sites server which may make remote code execution possible.
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, 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
Reaching this weakness in Omni Secure Files <= 0.1.13 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 Omni Secure Files the fix is 0.1.14: builds <= 0.1.13 are affected, anything from 0.1.14 onward is not.
Remediation
Update to version 0.1.14, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Omni Secure Files: 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: Omni Secure Files 0.1.14 closes this, and updating the plugin is the step that ends it.
- Firewall
- Scanner
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C