Skip to main content
Mallory
CriticalPublic exploitVulnerability

CVE-2012-10020: Arbitrary File Upload in FoxyPress WordPress Plugin uploadify.php

Published Jul 22, 2025 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS9.8Critical · v3.1
EPSS4.8%92nd percentile
CISA KEVNoNot listed
In the wildNonePublic exploit, no exploitation reported
Vendor
Webmovementllc
IdentifiersCVE-2012-10020CWE-434 · Unrestricted Upload of File with…

CVE-2012-10020 affects the FoxyPress plugin for WordPress in versions up to and including 0.4.2.1. The vulnerability is caused by missing file type validation in the plugin's uploadify.php file, allowing an unauthenticated attacker to upload arbitrary files to the server hosting the affected WordPress site. Because the upload mechanism does not properly restrict uploaded content to safe file types, an attacker may be able to place executable server-side files on the system, which can lead to remote code execution depending on server configuration and upload location.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows unauthenticated arbitrary file upload to the affected server. If the uploaded file is a server-executable payload and it is placed in a web-accessible or otherwise executable location, the attacker may achieve remote code execution in the context of the web server or WordPress application. This can result in full site compromise, unauthorized modification of site content, theft of sensitive data, deployment of malware or web shells, and potential pivoting to other resources accessible from the compromised host.

Mitigation

If you can’t patch tonight, do this now.

Restrict direct access to the vulnerable uploadify.php endpoint using web server rules, WAF controls, authentication, or IP allowlisting where operationally feasible. Disable execution of scripts in upload directories, enforce least-privilege filesystem permissions, and monitor for suspicious file uploads and newly created executable files in web-accessible paths. Additional mitigations include disabling or uninstalling the plugin until a fix is applied and using server-side controls to block dangerous extensions from being uploaded or executed.

Remediation

Patch, then assume compromise.

Update the FoxyPress plugin to a version newer than 0.4.2.1 if a fixed release is available. If no patched version is available, remove or disable the FoxyPress plugin, especially the vulnerable uploadify.php functionality. Review the server for unauthorized uploaded files, including web shells and other executable payloads, and remove any malicious artifacts. Validate that upload handlers enforce strict allowlisting of permitted file types, verify MIME types and extensions server-side, and store uploads outside executable web paths where possible.

Exposure surface

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
WebmovementllcFoxypressapplication
FAQ

Frequently asked questions

Is CVE-2012-10020 exploited in the wild?
As of Sep 25, 2026, Mallory has no reports of CVE-2012-10020 being exploited in the wild. It is not listed in CISA KEV.
Is there a public exploit for CVE-2012-10020?
Yes. Mallory tracks 1 public exploit or proof of concept for CVE-2012-10020, the earliest disclosed Jun 5, 2012.
Is there a patch for CVE-2012-10020?
Update the FoxyPress plugin to a version newer than 0.4.2.1 if a fixed release is available. If no patched version is available, remove or disable the FoxyPress plugin, especially the vulnerable uploadify.php functionality.
What products are affected by CVE-2012-10020?
Webmovementllc Foxypress.
How severe is CVE-2012-10020?
CVE-2012-10020 has a CVSS v3.1 score of 9.8 (Critical) and an EPSS score of 4.8% (92nd percentile) as of Sep 25, 2026.
Activity feed

Recent activity

7 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

View more in app →

No news coverage yet. Advisories and community discussion only.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity7Community discussion across Reddit, Mastodon, and other social sources.