WordPress up to 2.0.4 mod_mime functions.php wp_check_filetype code injection
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in WordPress up to 2.0.4. Affected by this issue is the function wp_check_filetype of the file /wp-includes/functions.php of the component mod_mime. The manipulation results in code injection.
This vulnerability is reported as CVE-2009-3890. Moreover, an exploit is present.
Upgrading the affected component is recommended.
Details
A vulnerability classified as critical has been found in WordPress up to 2.0.4 (Content Management System). Affected is the function wp_check_filetype of the file /wp-includes/functions.php of the component mod_mime. The manipulation with an unknown input leads to a code injection vulnerability. CWE is classifying the issue as CWE-94. The product constructs all or part of a code segment using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the syntax or behavior of the intended code segment. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
Unrestricted file upload vulnerability in the wp_check_filetype function in wp-includes/functions.php in WordPress before 2.8.6, when a certain configuration of the mod_mime module in the Apache HTTP Server is enabled, allows remote authenticated users to execute arbitrary code by posting an attachment with a multiple-extension filename, and then accessing this attachment via a direct request to a wp-content/uploads/ pathname, as demonstrated by a .php.jpg filename.
The weakness was disclosed 11/12/2009 by Dawid Golunski (oss-sec). The advisory is shared for download at openwall.com. This vulnerability is traded as CVE-2009-3890 since 11/05/2009. It is possible to launch the attack remotely. The requirement for exploitation is a authentication. Technical details and a public exploit are known. The MITRE ATT&CK project declares the attack technique as T1059.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept. As 0-day the estimated underground price was around $5k-$25k. By approaching the search of inurl:wp-includes/functions.php it is possible to find vulnerable targets with Google Hacking. The vulnerability scanner Nessus provides a plugin with the ID 42808 (FreeBSD : wordpress -- multiple vulnerabilities (0640198a-d117-11de-b667-0030843d3802)), which helps to determine the existence of the flaw in a target environment. It is assigned to the family FreeBSD Local Security Checks. The commercial vulnerability scanner Qualys is able to test this issue with plugin 116849 (Fedora Update for wordpress-mu (FEDORA-2009-12547)).
Upgrading to version 2.0.5 eliminates this vulnerability. A possible mitigation has been published before and not just after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at X-Force (54255), Exploit-DB (10089), Tenable (42808), SecurityFocus (BID 37005†) and OSVDB (59958†). The entry VDB-50833 is pretty similar. VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Name
Version
License
Website
- Product: https://wordpress.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 5.7
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔍
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔍
VulDB Temp Score: 🔍
VulDB Reliability: 🔍
NVD Base Score: 🔍
Exploiting
Class: Code injectionCWE: CWE-94 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Access: Public
Status: Proof-of-Concept
Download: 🔍
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Nessus ID: 42808
Nessus Name: FreeBSD : wordpress -- multiple vulnerabilities (0640198a-d117-11de-b667-0030843d3802)
Nessus File: 🔍
Nessus Risk: 🔍
Nessus Family: 🔍
Nessus Port: 🔍
OpenVAS ID: 66272
OpenVAS Name: FreeBSD Ports: wordpress
OpenVAS File: 🔍
OpenVAS Family: 🔍
Qualys ID: 🔍
Qualys Name: 🔍
Exploit-DB: 🔍
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: WordPress 2.0.5
Timeline
11/05/2009 🔍11/11/2009 🔍
11/11/2009 🔍
11/12/2009 🔍
11/12/2009 🔍
11/13/2009 🔍
11/13/2009 🔍
11/16/2009 🔍
11/17/2009 🔍
11/24/2009 🔍
03/18/2015 🔍
09/16/2025 🔍
Sources
Product: wordpress.comAdvisory: openwall.com
Researcher: Dawid Golunski
Status: Confirmed
Confirmation: 🔍
CVE: CVE-2009-3890 (🔍)
GCVE (CVE): GCVE-0-2009-3890
GCVE (VulDB): GCVE-100-50832
X-Force: 54255
SecurityFocus: 37005 - WordPress 'wp-admin/includes/file.php' Arbitrary File Upload Vulnerability
Secunia: 37332 - WordPress File Upload and Script Insertion, Less Critical
OSVDB: 59958 - WordPress /wp-includes/functions.php wp_check_filetype() Function File Upload Arbitrary Code Execution
Vulnerability Center: 24173 - WordPress < 2.8.6 Remote Arbitrary Code Execution Vulnerability via Multiple-Extension Filename, Medium
scip Labs: https://www.scip.ch/en/?labs.20161013
See also: 🔍
Entry
Created: 03/18/2015 15:15Updated: 09/16/2025 20:09
Changes: 03/18/2015 15:15 (71), 08/15/2017 09:26 (13), 08/27/2021 22:25 (3), 09/16/2025 20:09 (25)
Complete: 🔍
Cache ID: 216::103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.