Skip to content
Fencer Intel
critical 9.8

CVE-2012-10020 json

FoxyPress <= 0.4.2.1 - Arbitrary File Upload

published 2025-07-22 15 mo ago modified 2026-06-16 4 mo ago also EUVD-2012-6566

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
4.8%
EPSS 4.8% chance of exploitation in 30 days, percentile 91%
public exploits
1
Metasploit

Summary

The FoxyPress plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the uploadify.php file in versions up to, and including, 0.4.2.1. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected sites server which may make remote code execution possible.

Patch / fix

  • WebMovementLLC FoxyPress 0.4.2.2

Timeline

  1. First public exploit (Metasploit exploit/unix/webapp/wp_foxypress_upload)
  2. Published

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
15 mo ago

Exploit prediction

4.78% chance of exploitation in the next 30 days, higher than 91% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/unix/webapp/wp_foxypress_upload WordPress Plugin Foxypress uploadify.php Arbitrary Code Execution metasploit exploit, excellent rank, 2012-06-05
  • packetstormsecurity.com https://packetstormsecurity.com/files/113576/ referenced PoC, tagged "exploit" by a source, unverified
  • web.archive.org https://web.archive.org/web/20210120060045/https%3A//www.securityfocus.com/bid/53805/info referenced PoC, tagged "exploit" by a source, unverified
  • raw.githubusercontent.com https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/unix/webapp/wp_foxypress_upload.rb referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • WebMovementLLC FoxyPress

Classification

Weakness
  • CWE-434 Unrestricted Upload of File with Dangerous Type
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.