WordPress component: Cross-site scripting
WordPress component is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
- Component
- WordPress component
- Plugin slug
- Not applicable
- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Sep 12, 2013
Update, patch or deactivate.
Update WordPress component 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
The get_allowed_mime_types function in wp-includes/functions.php in WordPress before 3.6.1 does not require the unfiltered_html capability for uploads of .htm and .html files, which might make it easier for remote authenticated users to conduct cross-site scripting (XSS) attacks via a crafted file.
NVD vector: AV:N/AC:M/Au:N/C:N/I:P/A:N
Primary and upstream sources
- NVD record for CVE-2013-5738
- WordPress upstream reference codex.wordpress.org
- WordPress upstream reference core.trac.wordpress.org
- WordPress upstream reference wordpress.org
- Upstream reference debian.org
- WordPress upstream reference codex.wordpress.org
- WordPress upstream reference core.trac.wordpress.org
- WordPress upstream reference wordpress.org
- Upstream reference debian.org