| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 3.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Piwik up to 0.2.6. It has been rated as problematic. This vulnerability affects unknown code. This manipulation causes cross site scripting. This vulnerability appears as CVE-2011-0004. The attack may be initiated remotely. There is no available exploit. Upgrading the affected component is advised.
Details
A vulnerability has been found in Piwik up to 0.2.6 and classified as problematic. Affected by this vulnerability is an unknown function. The manipulation with an unknown input leads to a cross site scripting vulnerability. The CWE definition for the vulnerability is 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. As an impact it is known to affect integrity. The summary by CVE is:
Multiple cross-site scripting (XSS) vulnerabilities in Piwik before 1.1 allow remote attackers to inject arbitrary web script or HTML via unspecified vectors.
The weakness was presented 01/04/2011 by Stefan Esser (Website). The advisory is shared at piwik.org. This vulnerability is known as CVE-2011-0004 since 12/07/2010. The attack can be launched remotely. The exploitation doesn't need any form of authentication. 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.
It is declared as proof-of-concept.
Upgrading to version 0.2.7 eliminates this vulnerability. A possible mitigation has been published immediately after the disclosure of the vulnerability.
The vulnerability is also documented in the databases at SecurityFocus (BID 45659†), OSVDB (70310†) and Secunia (SA42809†). See VDB-55997, VDB-55996, VDB-55995 and VDB-55994 for similar entries. Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 3.9
VulDB Base Score: 4.3
VulDB Temp Score: 3.9
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: Proof-of-Concept
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: Piwik 0.2.7
Timeline
12/07/2010 🔍01/04/2011 🔍
01/04/2011 🔍
01/04/2011 🔍
01/07/2011 🔍
01/10/2011 🔍
03/19/2015 🔍
02/08/2019 🔍
Sources
Advisory: piwik.orgResearcher: Stefan Esser
Status: Not defined
Confirmation: 🔍
CVE: CVE-2011-0004 (🔍)
GCVE (CVE): GCVE-0-2011-0004
GCVE (VulDB): GCVE-100-55993
SecurityFocus: 45659 - Piwik Unspecified Cross-site scripting and Unspecified HTML Injection Vulnerabilities
Secunia: 42809
OSVDB: 70310 - Piwik Unspecified Multiple XSS
Vupen: ADV-2011-0013
See also: 🔍
Entry
Created: 03/19/2015 23:27Updated: 02/08/2019 14:54
Changes: 03/19/2015 23:27 (52), 02/08/2019 14:54 (7)
Complete: 🔍
Cache ID: 216:671:103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.