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 10, 2009
This CVE was published Jul 10, 2009 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
WordPress and WordPress MU before 2.8.1 allow remote attackers to obtain sensitive information via a direct request to wp-settings.php, which reveals the installation path in an error message.
NVD vector: AV:N/AC:L/Au:N/C:P/I:N/A:N
Primary and upstream sources
- NVD record for CVE-2009-2432
- Upstream reference corelabs.coresecurity.com
- Upstream reference securitytracker.com
- Upstream reference osvdb.org
- Upstream reference securityfocus.com
- Upstream reference vupen.com
- Upstream reference exchange.xforce.ibmcloud.com
- Upstream reference corelabs.coresecurity.com
- Upstream reference securitytracker.com
- Upstream reference osvdb.org
- Upstream reference securityfocus.com
- Upstream reference vupen.com
- Upstream reference exchange.xforce.ibmcloud.com