CVE-2013-2204
Tinymce Media vulnerability
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.
Affected products
Media, Wordpress. The exact versions are in the references.
What to do now
- Check your exposureFind out whether Tinymce Media runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Limit access until thenIf you cannot update at once, take the system off the internet or restrict who can reach it.
References
- wordpress.org/news/2013/06/wordpress-3-5-2/ · Vendor Advisory
- github.com/moxiecode/moxieplayer/commit/b61ac518ffa2657e2dc9019b2dcf2f3f37dbfab0 · Exploit
- codex.wordpress.org/Version_3.5.2
- www.debian.org/security/2013/dsa-2718
- bugzilla.redhat.com/show_bug.cgi?id=976784
- nvd.nist.gov/vuln/detail/CVE-2013-2204
- cve.org/CVERecord?id=CVE-2013-2204
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.