CVE-2013-2204: Input Validation

Published Jul 8, 2013
·
Updated

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 QUERYSTRING, 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 Software

78 affected components
TinyMCE Media
WordPress WordPress<=3.5.1
WordPress WordPress=0.71
WordPress WordPress=1.0
WordPress WordPress=1.0.1
WordPress WordPress=1.0.2
WordPress WordPress=1.1.1
WordPress WordPress=1.2
WordPress WordPress=1.2.1
WordPress WordPress=1.2.2
WordPress WordPress=1.2.3
WordPress WordPress=1.2.4
WordPress WordPress=1.2.5
WordPress WordPress=1.2.5-a
WordPress WordPress=1.3
WordPress WordPress=1.3.2
WordPress WordPress=1.3.3
WordPress WordPress=1.5
WordPress WordPress=1.5.1
WordPress WordPress=1.5.1.1
WordPress WordPress=1.5.1.2
WordPress WordPress=1.5.1.3
WordPress WordPress=1.5.2
WordPress WordPress=1.6.2
WordPress WordPress=2.0
WordPress WordPress=2.0.1
WordPress WordPress=2.0.2
WordPress WordPress=2.0.4
WordPress WordPress=2.0.5
WordPress WordPress=2.0.6
WordPress WordPress=2.0.7
WordPress WordPress=2.0.8
WordPress WordPress=2.0.9
WordPress WordPress=2.0.10
WordPress WordPress=2.0.11
WordPress WordPress=2.1
WordPress WordPress=2.1.1
WordPress WordPress=2.1.2
WordPress WordPress=2.1.3
WordPress WordPress=2.2
WordPress WordPress=2.2.1
WordPress WordPress=2.2.2
WordPress WordPress=2.2.3
WordPress WordPress=2.3
WordPress WordPress=2.3.1
WordPress WordPress=2.3.2
WordPress WordPress=2.3.3
WordPress WordPress=2.5
WordPress WordPress=2.5.1
WordPress WordPress=2.6
WordPress WordPress=2.6.1
WordPress WordPress=2.6.2
WordPress WordPress=2.6.3
WordPress WordPress=2.6.5
WordPress WordPress=2.7
WordPress WordPress=2.7.1
WordPress WordPress=2.8
WordPress WordPress=2.8.1
WordPress WordPress=2.8.2
WordPress WordPress=2.8.3
WordPress WordPress=2.8.4
WordPress WordPress=2.8.4-a
WordPress WordPress=2.8.5
WordPress WordPress=2.8.5.1
WordPress WordPress=2.8.5.2
WordPress WordPress=2.8.6
WordPress WordPress=2.9
WordPress WordPress=2.9.1
WordPress WordPress=2.9.1.1
WordPress WordPress=2.9.2
WordPress WordPress=3.3
WordPress WordPress=3.3.1
WordPress WordPress=3.3.2
WordPress WordPress=3.3.3
WordPress WordPress=3.4.0
WordPress WordPress=3.4.1
WordPress WordPress=3.4.2
WordPress WordPress=3.5.0

Event History

Jul 8, 2013
CVE Published
via MITRE·08:00 PM
Data Sourced
via MITRE·08:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2013-2204?

CVE-2013-2204 is categorized as having a moderate severity level.

2

How do I fix CVE-2013-2204?

To fix CVE-2013-2204, update your WordPress installation to version 3.5.2 or later.

3

What products are affected by CVE-2013-2204?

CVE-2013-2204 affects WordPress versions prior to 3.5.2 and the TinyMCE Media plugin.

4

Can exploiting CVE-2013-2204 lead to remote code execution?

Yes, exploiting CVE-2013-2204 allows attackers to pass arbitrary parameters to a Flash application potentially leading to unauthorized actions.

5

Is there a workaround for CVE-2013-2204?

A recommended workaround for CVE-2013-2204 is to disable the TinyMCE Media plugin until the software can be updated.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203