WordPress 1.2.2/2.2.0 File Upload wp-app.php privilege escalation
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, has been found in WordPress 1.2.2/2.2.0. Affected is an unknown function of the file wp-app.php of the component File Upload. The manipulation leads to privilege escalation. This vulnerability is traded as CVE-2007-3544. There is no exploit available.
Details
A vulnerability was found in WordPress 1.2.2/2.2.0 (Content Management System). It has been rated as critical. This issue affects an unknown functionality of the file wp-app.php of the component File Upload. The manipulation with an unknown input leads to a privilege escalation vulnerability. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
The weakness was shared 06/23/2007 (Website). It is possible to read the advisory at buayacorp.com. The identification of this vulnerability is CVE-2007-3544 since 07/03/2007. The exploitation is known to be easy. The attack may be initiated remotely. The successful exploitation needs a simple authentication. Technical details of the vulnerability are known, but there is no available exploit.
By approaching the search of inurl:wp-app.php it is possible to find vulnerable targets with Google Hacking.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the databases at OSVDB (37294†) and Secunia (SA25794†). The entry VDB-3151 is related to this item. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
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: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
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: Privilege escalationCWE: Unknown
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
Google Hack: 🔍
EPSS Score: 🔍
EPSS Percentile: 🔍
Price Prediction: 🔍
Current Price Estimation: 🔍
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔍
Timeline
06/23/2007 🔍06/26/2007 🔍
06/26/2007 🔍
07/03/2007 🔍
07/03/2007 🔍
03/15/2015 🔍
09/05/2018 🔍
Sources
Product: wordpress.comAdvisory: buayacorp.com
Status: Not defined
CVE: CVE-2007-3544 (🔍)
GCVE (CVE): GCVE-0-2007-3544
GCVE (VulDB): GCVE-100-37619
Secunia: 25794 - WordPress Custom Field PHP Script Upload, Moderately Critical
OSVDB: 37294 - WordPress / MU Multiple Script Unrestricted File Upload
See also: 🔍
Entry
Created: 03/15/2015 15:58Updated: 09/05/2018 07:22
Changes: 03/15/2015 15:58 (45), 09/05/2018 07:22 (8)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.