CVE-2009-3890: Code Injection

Published Nov 17, 2009
·
Updated

Unrestricted file upload vulnerability in the wpcheckfiletype function in wp-includes/functions.php in WordPress before 2.8.6, when a certain configuration of the modmime 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.

Affected Software

1 affected component
WordPress<=2.8.5

Event History

Nov 17, 2009
CVE Published
via MITRE·06:00 PM
Data Sourced
via MITRE·06:00 PM
Description

Frequently Asked Questions

1

What is the severity of CVE-2009-3890?

CVE-2009-3890 has a high severity due to its potential to allow remote authenticated users to execute arbitrary code.

2

How do I fix CVE-2009-3890?

To fix CVE-2009-3890, upgrade WordPress to version 2.8.6 or later.

3

Who is affected by CVE-2009-3890?

CVE-2009-3890 affects users of WordPress versions prior to 2.8.6 with specific Apache mod_mime configurations.

4

What type of vulnerability is CVE-2009-3890?

CVE-2009-3890 is classified as an unrestricted file upload vulnerability.

5

Can CVE-2009-3890 be exploited without authentication?

No, CVE-2009-3890 requires remote authenticated users to exploit the vulnerability.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203