CVE-2013-2204Not scoredCWE-20

CVE-2013-2204: Tinymce Media vulnerability

Tinymce · Media

Fixed in 3.5.2 · Affected: Tinymce Media before 3.5.2 · Exploitation: possible (1 to 10%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

2.9%probability of exploitation in the next 30 days

87th percentile

050100

Higher than 87% of scored CVEs

Not scored yet. The CVE record carries no CVSS score.

DescriptionCVE.org

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.

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Possible (1 to 10%). EPSS between 1% and 10%.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Improper Input Validation · Input Validation and Logic
Vendor: Tinymce
Published: July 2013
Band: Possible (1 to 10%), July 2013

CoverageNo articles yet

No CyberSIXT article names CVE-2013-2204 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.