Patrick Przybilla AddToAny 6.x-3.0/6.x-3.1/6.x-3.2/6.x-3.3/6.x-3.x cross site scripting
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.4 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Patrick Przybilla AddToAny 6.x-3.0/6.x-3.1/6.x-3.2/6.x-3.3/6.x-3.x. This issue affects some unknown processing. The manipulation leads to cross site scripting. This vulnerability is uniquely identified as CVE-2012-2072. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability was found in Patrick Przybilla AddToAny 6.x-3.0/6.x-3.1/6.x-3.2/6.x-3.3/6.x-3.x and classified as problematic. This issue affects some unknown functionality. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. The summary by CVE is:
Cross-site scripting (XSS) vulnerability in the Share Buttons (AddToAny) module 6.x-3.x before 6.x-3.4 for Drupal allows remote authenticated users with the administer addtoany permission to inject arbitrary web script or HTML via unspecified vectors.
The weakness was disclosed 08/14/2012 (Website). The advisory is shared at drupal.org. The identification of this vulnerability is CVE-2012-2072 since 04/04/2012. The exploitation is known to be difficult. The attack may be initiated remotely. A simple authentication is required for exploitation. It demands that the victim is doing some kind of user interaction. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1059.007 for this issue.
Upgrading to version 6.x-3.3 eliminates this vulnerability.
The vulnerability is also documented in the databases at X-Force (74469), SecurityFocus (BID 52777†), OSVDB (80675†) and Secunia (SA48615†). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 3.5VulDB Meta Temp Score: 3.4
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
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 scriptingCWE: CWE-79 / CWE-94 / CWE-74
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: AddToAny 6.x-3.3
Timeline
03/29/2012 🔍03/29/2012 🔍
04/04/2012 🔍
08/14/2012 🔍
08/14/2012 🔍
03/23/2015 🔍
02/19/2019 🔍
Sources
Advisory: drupal.orgStatus: Not defined
Confirmation: 🔍
CVE: CVE-2012-2072 (🔍)
GCVE (CVE): GCVE-0-2012-2072
GCVE (VulDB): GCVE-100-61637
X-Force: 74469
SecurityFocus: 52777 - Drupal Share Buttons (AddToAny) Module Unspecified Cross Site Scripting Vulnerability
Secunia: 48615 - Drupal Share Buttons (AddToAny) Module Unspecified Script Insertion Vulnerability, Less Critical
OSVDB: 80675
Entry
Created: 03/23/2015 16:50Updated: 02/19/2019 19:49
Changes: 03/23/2015 16:50 (57), 02/19/2019 19:49 (1)
Complete: 🔍
Cache ID: 216:510:103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.