Security readout for executives and security teams
Plain-English summary
FoxyPress for WordPress allowed unauthenticated visitors to upload arbitrary files because its upload handler did not validate file types. On an exposed site, that can lead to server compromise if an attacker uploads executable content. This is critical for any site still running FoxyPress through version 0.4.2.1.
Executive priority
Prioritize any affected internet-facing WordPress site immediately. The business risk is full site takeover, data theft, defacement, or malware hosting. If FoxyPress is unused or unmaintained, removal is the lowest-risk path.
Technical view
CVE-2012-10020 is a CWE-434 arbitrary file upload flaw in FoxyPress uploadify.php affecting versions up to 0.4.2.1. The CVSS 3.1 score is 9.8 because network attackers need no authentication or user interaction, and successful exploitation may enable remote code execution.
Likely exposure
Exposure is limited to WordPress sites with the FoxyPress plugin installed at version 0.4.2.1 or earlier. Internet-facing WordPress deployments are the primary concern. The source bundle does not establish impact for other products or later versions.
Exploitation context
The bundle references Packet Storm and a Metasploit module, so public exploit material exists. KEV is false, and the provided sources do not prove active exploitation in the wild. Treat exposed legacy installations as urgent because exploitation requires no authentication.
Researcher notes
Do not assume current exploitation from this bundle alone. Focus validation on plugin presence, version, upload handler exposure, and post-compromise indicators. The WordPress Trac changeset is relevant for remediation research, but the bundle does not name a specific fixed version.
Mitigation direction
- Inventory WordPress sites for FoxyPress and record the installed version.
- Disable or remove FoxyPress versions 0.4.2.1 and earlier until remediated.
- Check WordPress plugin repository or vendor guidance for a maintained fixed release.
- Prevent script execution from writable upload directories where supported.
- Review webroot and upload paths for unexpected executable files.
Validation and detection
- Confirm whether FoxyPress is installed on each WordPress instance.
- Verify plugin version is not 0.4.2.1 or earlier.
- Inspect server logs for unauthenticated upload requests to uploadify.php.
- Review filesystem timestamps for recent unexpected files in upload locations.
- Confirm web server policy blocks execution from upload directories.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2012-10020 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.8 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
9.8CriticalVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Source materials
- CVE List V5 sourceCVE List V5
- https://www.wordfence.com/threat-intel/vulnerabilities/id/8fbc88da-8944-433c-b94d-9604ffe13d8a?source=cveCVE reference
- https://packetstormsecurity.com/files/113576/CVE reference
- https://web.archive.org/web/20210120060045/https%3A//www.securityfocus.com/bid/53805/infoCVE reference
- https://plugins.trac.wordpress.org/changeset/555071CVE reference
- https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/unix/webapp/wp_foxypress_upload.rbCVE reference
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.