Nmedia WordPress Member Conversation < 1.4 - Arbitrary File Upload
Strategic Overview
- Status
- Patched in 1.4
- Affected Plugin
- Nmedia WordPress Member Conversation
- Affected Version
< 1.4- CVSS
- 9.8Critical
- Weakness type
- CWE-434 · Unrestricted Upload of File with Dangerous Type
- CVE
CVE-2012-3577
At a glance
CVE-2012-3577 is a critical-severity Unrestricted Upload of File with Dangerous Type vulnerability in the Nmedia WordPress Member Conversation WordPress plugin, affecting versions < 1.4. 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 1.4; sites on affected versions should update now. Disclosed June 2012, reported by Sammy Forgit.
Vulnerability Overview
Unrestricted file upload vulnerability in doupload.php in the Nmedia Member Conversation plugin before 1.4 for WordPress allows remote attackers to execute arbitrary code by uploading a file with an executable extension, then accessing it via a direct request to the file in wp-content/uploads/user_uploads.
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 Nmedia WordPress Member Conversation < 1.4 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 Nmedia WordPress Member Conversation the fix is 1.4: builds < 1.4 are affected, anything from 1.4 onward is not.
Remediation
Update to version 1.4, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Nmedia WordPress Member Conversation: 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: Nmedia WordPress Member Conversation 1.4 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