WordPress component: A security weakness

WordPress component is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 6.0 CVSS · secalert@redhat.com

NVD score 6.0 CVSS 2.0 · nvd@nist.gov

Component: WordPress component
Plugin slug: Not applicable
Affected: See vendor advisory
Safe version: See mitigation notes
Published: Nov 17, 2009
Weakness: CWE-94 — Improper Control of Generation of Code ('Code Injection')

What to do

Update, patch or deactivate.

Update WordPress component to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

NVD vector: AV:N/AC:M/Au:S/C:P/I:P/A:P

References

Update, patch or deactivate.

Technical description

Primary and upstream sources