CVE-2007-3544

WordPress Core <= 2.2.1 - Arbitrary File Upload

2007-08-05 00:00
Anonymous

Strategic Overview

Status
Patched in 1.2.4
Affected Core
WordPress 1.2
Affected Version
<= 1.2.3
CVSS
8.8High
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2007-3544
View all WordPress 1.2 vulnerabilities

At a glance

CVE-2007-3544 is a high-severity Unrestricted Upload of File with Dangerous Type vulnerability in the WordPress 1.2 WordPress release line, affecting <= 1.2.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 1.2.4; sites on affected versions should update now. Disclosed August 2007.

Vulnerability Overview

Unrestricted file upload vulnerability in (1) wp-app.php and (2) app.php in WordPress 2.2.1 and WordPress MU 1.2.3 allows remote authenticated users to upload and execute arbitrary PHP code via unspecified vectors, possibly related to the wp_postmeta table and the use of custom fields in normal (non-attachment) posts. NOTE: this issue reportedly exists because of an incomplete fix for CVE-2007-3543.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in WordPress 1.2 <= 1.2.3 takes a caller who can reach the endpoint. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. For WordPress 1.2 the fix is 1.2.4: builds <= 1.2.3 are affected, anything from 1.2.4 onward is not.

Remediation

Update to version 1.2.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WordPress 1.2: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: updating to 1.2.4 is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2007-3544https://www.wordfence.com/threat-intel/vulnerabilities/id/0848d526-9530-40f3-8430-499d96b9a1b1https://nvd.nist.gov/vuln/detail/CVE-2007-3544

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C