Wordpress Mu: A security weakness
Wordpress Mu is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
- Component
- Wordpress Mu
- Plugin slug
wordpress-mu- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Jul 03, 2007
- Weakness
- NVD-CWE-Other
This CVE was published Jul 03, 2007 and is one of 10 known issues for this plugin.
Update, patch or deactivate.
Update Wordpress Mu to a release outside the affected range, or disable and remove it until a fixed version is available.
No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
Unrestricted file upload vulnerability in WordPress before 2.2.1 and WordPress MU before 1.2.3 allows remote authenticated users to upload and execute arbitrary PHP code by making a post that specifies a .php filename in the _wp_attached_file metadata field; and then sending this file's content, along with its post_ID value, to (1) wp-app.php or (2) app.php.
NVD vector: AV:N/AC:M/Au:S/C:P/I:P/A:P
Primary and upstream sources
- NVD record for CVE-2007-3543
- Upstream reference osvdb.org
- Upstream reference secunia.com
- WordPress upstream reference trac.mu.wordpress.org
- Upstream reference buayacorp.com
- Upstream reference securityfocus.com
- Upstream reference osvdb.org
- Upstream reference secunia.com
- WordPress upstream reference trac.mu.wordpress.org
- Upstream reference buayacorp.com
- Upstream reference securityfocus.com