WordPress WordPress mu up to 1.0 wp-newblog.php weblog_id cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 0.00 |
Summary
A vulnerability was found in WordPress WordPress mu up to 1.0. It has been declared as problematic. This impacts an unknown function of the file wp-newblog.php. The manipulation of the argument weblog_id results in cross-site request forgery. This vulnerability is known as CVE-2007-4544. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability classified as problematic has been found in WordPress WordPress mu up to 1.0 (Content Management System). Affected is some unknown processing of the file wp-newblog.php. The manipulation of the argument weblog_id with an unknown input leads to a cross-site request forgery vulnerability. CWE is classifying the issue as CWE-352. The web application does not, or can not, sufficiently verify whether a well-formed, valid, consistent request was intentionally provided by the user who submitted the request. This is going to have an impact on integrity. CVE summarizes:
Cross-site scripting (XSS) vulnerability in wp-newblog.php in WordPress multi-user (MU) 1.0 and earlier allows remote attackers to inject arbitrary web script or HTML via the weblog_id parameter (Username field).
The weakness was published 08/22/2007 (Website). The advisory is shared for download at securityvulns.ru. This vulnerability is traded as CVE-2007-4544 since 08/27/2007. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available.
By approaching the search of inurl:wp-newblog.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 vulnerability database at OSVDB (38442†). VulDB is the best source for vulnerability data and more expert information about this specific topic.
Product
Type
Vendor
Name
Version
License
Website
- Vendor: https://wordpress.com/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
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
08/22/2007 🔍08/27/2007 🔍
08/27/2007 🔍
11/08/2007 🔍
03/16/2015 🔍
10/29/2017 🔍
Sources
Vendor: wordpress.comAdvisory: securityvulns.ru
Status: Not defined
CVE: CVE-2007-4544 (🔍)
GCVE (CVE): GCVE-0-2007-4544
GCVE (VulDB): GCVE-100-38520
OSVDB: 38442 - WordPress / MU wp-newblog.php weblog_id Parameter XSS
Entry
Created: 03/16/2015 12:18Updated: 10/29/2017 11:59
Changes: 03/16/2015 12:18 (45), 10/29/2017 11:59 (6)
Complete: 🔍
Cache ID: 216:11F:103
VulDB is the best source for vulnerability data and more expert information about this specific topic.
No comments yet. Languages: en.
Please log in to comment.