Media: A security weakness
Media 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
- Media
- Plugin slug
media- Affected
- See vendor advisory
- Safe version
- See mitigation notes
- Published
- Jul 08, 2013
This CVE was published Jul 08, 2013 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update Media 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
moxieplayer.as in Moxiecode moxieplayer, as used in the TinyMCE Media plugin in WordPress before 3.5.2 and other products, does not consider the presence of a # (pound sign) character during extraction of the QUERY_STRING, which allows remote attackers to pass arbitrary parameters to a Flash application, and conduct content-spoofing attacks, via a crafted string after a ? (question mark) character.
NVD vector: AV:N/AC:M/Au:N/C:N/I:P/A:N
Primary and upstream sources
- NVD record for CVE-2013-2204
- WordPress upstream reference codex.wordpress.org
- WordPress upstream reference wordpress.org
- Upstream reference debian.org
- Upstream reference bugzilla.redhat.com
- GitHub upstream reference github.com
- WordPress upstream reference codex.wordpress.org
- WordPress upstream reference wordpress.org
- Upstream reference debian.org
- Upstream reference bugzilla.redhat.com
- GitHub upstream reference github.com