BestWebSoft Twitter Plugin up to 2.14 on WordPress Settings Page twitter.php twttr_settings_page cross-site request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.7 | $0-$5k | 0.00 |
Summary
A vulnerability categorized as problematic has been discovered in BestWebSoft Twitter Plugin up to 2.14 on WordPress. Affected by this issue is the function twttr_settings_page of the file twitter.php of the component Settings Page. The manipulation results in cross-site request forgery.
This vulnerability is cataloged as CVE-2012-10015. The attack may be launched remotely. There is no exploit available.
It is advisable to upgrade the affected component.
Details
A vulnerability was found in BestWebSoft Twitter Plugin up to 2.14 on WordPress (Social Network Software). It has been classified as problematic. Affected is the function twttr_settings_page of the file twitter.php of the component Settings Page. The manipulation 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.
The weakness was shared 07/24/2012 as a6d4659cbb2cbf18ccb0fb43549d5113d74e0146. The advisory is available at github.com. This vulnerability is traded as CVE-2012-10015. Successful exploitation requires user interaction by the victim. Technical details are known, but there is no available exploit.
By approaching the search of inurl:twitter.php it is possible to find vulnerable targets with Google Hacking.
Upgrading to version 2.15 eliminates this vulnerability. Applying the patch a6d4659cbb2cbf18ccb0fb43549d5113d74e0146 is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version. A possible mitigation has been published immediately after the disclosure of the vulnerability. The advisory contains the following remark:
Cross Site Request Forgery bug was fixed
If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Type
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.8VulDB Meta Temp Score: 5.7
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔍
CNA Base Score: 4.3
CNA Vector (VulDB): 🔍
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: UpgradeStatus: 🔍
Reaction Time: 🔍
0-Day Time: 🔍
Exposure Time: 🔍
Upgrade: Twitter Plugin 2.15
Patch: a6d4659cbb2cbf18ccb0fb43549d5113d74e0146
Timeline
07/24/2012 🔍07/24/2012 🔍
05/29/2023 🔍
05/29/2023 🔍
06/21/2023 🔍
Sources
Advisory: a6d4659cbb2cbf18ccb0fb43549d5113d74e0146Status: Confirmed
CVE: CVE-2012-10015 (🔍)
GCVE (CVE): GCVE-0-2012-10015
GCVE (VulDB): GCVE-100-230154
Entry
Created: 05/29/2023 17:43Updated: 06/21/2023 21:53
Changes: 05/29/2023 17:43 (48), 06/21/2023 21:43 (2), 06/21/2023 21:53 (28)
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.