CVE-2009-3890
What it is
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.
At a glance
- Exploitability
- Can be exploited over the network with a login. Limited direct impact.
- Exploit odds
- 8.7% chance of exploitation in the next 30 days (EPSS).
- Fix
- A patch, advisory or fixed version is referenced. Upgrade or apply it.
Timeline
- PublishedDisclosed publicly on CVE.org and NVD
- Last updatedMost recent change to the record
Why it ranks here
- Exploited in the wild: no, CISA does not list it.
- Exploit odds: 8.7% in the next 30 days (EPSS).
- Severity: 6.0 MEDIUM (CVSS).
- Fix: a patch or advisory is linked.
Details
- Published
- Last modified
- Exploit probability
- 8.7% · EPSS, next 30 days
- Weakness
- CWE-94 · Code injection
- Record status
- Modified
Affected
- WordPress ≤ 2.8.5
Attack profile CVSS 2.0 · 6.0
- Attack vector
- Network
- Complexity
- Medium
- Authentication
- Single
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
Raw vector
AV:N/AC:M/Au:S/C:P/I:P/A:P
Is it in your code?
Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.
Read https://cve-list.com/agent/cve/CVE-2009-3890.md and follow it. Check whether this project is affected by CVE-2009-3890. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.
Fix and advisories
- http://core.trac.wordpress.org/ticket/11122
- http://wordpress.org/development/2009/11/wordpress-2-8-6-security-release/
- http://core.trac.wordpress.org/ticket/11122
- http://wordpress.org/development/2009/11/wordpress-2-8-6-security-release/
References
- http://archives.neohapsis.com/archives/fulldisclosure/2009-11/0142.html
- http://archives.neohapsis.com/archives/fulldisclosure/2009-11/0149.html
- http://archives.neohapsis.com/archives/fulldisclosure/2009-11/0153.html
- http://core.trac.wordpress.org/ticket/11122
- http://secunia.com/advisories/37332
- http://wordpress.org/development/2009/11/wordpress-2-8-6-security-release/
- http://www.openwall.com/lists/oss-security/2009/11/15/2
- http://www.openwall.com/lists/oss-security/2009/11/15/3
- http://www.openwall.com/lists/oss-security/2009/11/16/1
- http://www.osvdb.org/59958
- http://archives.neohapsis.com/archives/fulldisclosure/2009-11/0142.html
- http://archives.neohapsis.com/archives/fulldisclosure/2009-11/0149.html
- http://archives.neohapsis.com/archives/fulldisclosure/2009-11/0153.html
- http://core.trac.wordpress.org/ticket/11122
- http://secunia.com/advisories/37332
- http://wordpress.org/development/2009/11/wordpress-2-8-6-security-release/
- http://www.openwall.com/lists/oss-security/2009/11/15/2
- http://www.openwall.com/lists/oss-security/2009/11/15/3
- http://www.openwall.com/lists/oss-security/2009/11/16/1
- http://www.osvdb.org/59958