WordPress component: A security weakness
WordPress component 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 component
- Plugin slug
Core- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Aug 10, 2011
- Weakness
- NVD-CWE-noinfo
This CVE was published Aug 10, 2011 and is one of 47 known issues for WordPress core.
Update, patch or deactivate.
No fixed release is identified. Update WordPress component when a confirmed fixed release becomes available; until then, disable and remove it when the site's risk warrants.
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
Unspecified vulnerability in WordPress 3.1 before 3.1.3 and 3.2 before Beta 2 has unknown impact and attack vectors related to "Media security."
NVD vector: AV:N/AC:L/Au:N/C:C/I:C/A:C
Primary and upstream sources
- NVD record for CVE-2011-3122
- Upstream reference secunia.com
- WordPress upstream reference wordpress.org
- Upstream reference debian.org
- Upstream reference securityfocus.com
- Upstream reference exchange.xforce.ibmcloud.com
- Upstream reference secunia.com
- WordPress upstream reference wordpress.org
- Upstream reference debian.org
- Upstream reference securityfocus.com
- Upstream reference exchange.xforce.ibmcloud.com