| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.3 | $0-$5k | 0.00 |
Summary
A vulnerability classified as problematic was found in WordPress 3.4.2. This affects an unknown part. Executing a manipulation can lead to cross-site request forgery. This vulnerability is tracked as CVE-2012-4448. The attack can be launched remotely. No exploit exists.
Details
A vulnerability has been found in WordPress 3.4.2 (Content Management System) and classified as critical. This vulnerability affects an unknown function. The manipulation with an unknown input leads to a cross-site request forgery vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect confidentiality, integrity, and availability. CVE summarizes:
Cross-site request forgery (CSRF) vulnerability in wp-admin/index.php in WordPress 3.4.2 allows remote attackers to hijack the authentication of administrators for requests that modify an RSS URL via a dashboard_incoming_links edit action.
The weakness was disclosed 09/28/2012 by AkaStep as Bug 860261 as not defined bug report (Bugzilla). The advisory is available at bugzilla.redhat.com. This vulnerability was named CVE-2012-4448 since 08/21/2012. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. Successful exploitation requires user interaction by the victim. The technical details are unknown and an exploit is not available.
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 X-Force (78744), SecurityFocus (BID 55795†), Secunia (SA50715†) and Vulnerability Center (SBV-38157†). If you want to get best quality of vulnerability data, you may have to visit VulDB.
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: Cross-site request forgeryCWE: CWE-352 / CWE-862 / CWE-863
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Not defined
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/21/2012 🔍09/22/2012 🔍
09/24/2012 🔍
09/24/2012 🔍
09/28/2012 🔍
09/28/2012 🔍
01/23/2013 🔍
03/24/2015 🔍
04/24/2017 🔍
Sources
Product: wordpress.comAdvisory: Bug 860261
Researcher: AkaStep
Status: Not defined
Confirmation: 🔍
CVE: CVE-2012-4448 (🔍)
GCVE (CVE): GCVE-0-2012-4448
GCVE (VulDB): GCVE-100-62482
X-Force: 78744
SecurityFocus: 55795 - WordPress 'wp-admin/index.php' Cross-Site Request Forgery Vulnerability
Secunia: 50715 - WordPress Cross-Site Request Forgery Vulnerability, Less Critical
Vulnerability Center: 38157 - WordPress 3.4.2 wp-admin/index.php Cross-Site Request Forgery Vulnerability, Medium
Entry
Created: 03/24/2015 12:22Updated: 04/24/2017 09:49
Changes: 03/24/2015 12:22 (57), 04/24/2017 09:49 (7)
Complete: 🔍
Cache ID: 216::103
If you want to get best quality of vulnerability data, you may have to visit VulDB.
No comments yet. Languages: en.
Please log in to comment.