CVE-2013-2204: moxieplayer.as in Moxiecode moxieplayer, as used in the TinyMCE Media plugin in WordPress before 3.5.2 and oth

Q: How do I fix CVE-2013-2204?

media: mitigate or apply the listed mitigation; wordpress: upgrade to newer than 3.5.1. Exact commands for each OS are on this page.

Q: Is CVE-2013-2204 being exploited?

CVE-2013-2204 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2013-2204 affect?

CVE-2013-2204 affects media, wordpress. Severity is medium (CVSS 4.3). 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 remo

Q: How urgent is CVE-2013-2204?

Priority 42/100. Public exploit reference

This month

MEDIUM 4.3MITIGATEUPGRADE

CVE-2013-2204 is a medium-severity flaw (CVSS 4.3) affecting media, wordpress. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	4.3 (Medium)
EPSS exploit chance	2.9% (top 13%)
CISA exploited list	No
Weakness	CWE-20
Published	2013-07-08
Last modified	2026-06-16

Publisher (CNA): Red Hat, Inc. · Vendor: tinymce · wordpress

Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2013-07-08 20:55 UTCPublished CVE record published
2026-06-16 23:52 UTCUpdated Record last modified

tinymce media MITIGATE

Affected: all versions

Fixed in: no fixed release known

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy media || rpm -q media || media --version

No fixed or unaffected release known

Apply the vendor mitigation from the advisory, disable the affected feature, or restrict network access.

wordpress wordpress UPGRADE

Affected: <= 3.5.1 · 0.71 · 1.0 · 1.0.1 · 1.0.2 · 1.1.1 · 1.2 · 1.2.1

Fixed in: newer than 3.5.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wordpress || rpm -q wordpress || wordpress --version

2. UPGRADE to newer than 3.5.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wordpress

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wordpress

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2013-2204?

media: mitigate or apply the listed mitigation; wordpress: upgrade to newer than 3.5.1. Exact commands for each OS are on this page.

Is CVE-2013-2204 being exploited?

CVE-2013-2204 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2013-2204 affect?

CVE-2013-2204 affects media, wordpress. Severity is medium (CVSS 4.3). 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 remo

How urgent is CVE-2013-2204?

Priority 42/100. Public exploit reference

Software pages

WordPress vulnerabilities

References

← Back to latest CVEs