| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.9 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as critical, was found in mystats 1.0.8. Affected is an unknown function of the file mystats.php. The manipulation of the argument Details results in sql injection. This vulnerability is cataloged as CVE-2006-6402. The attack may be launched remotely. There is no exploit available.
Details
A vulnerability classified as critical has been found in mystats 1.0.8. Affected is some unknown functionality of the file mystats.php. The manipulation of the argument details with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability. CVE summarizes:
SQL injection vulnerability in mystats.php in MyStats 1.0.8 and earlier allows remote attackers to execute arbitrary SQL commands via the details parameter.
The weakness was shared 11/12/2006 (Website). The advisory is available at vupen.com. This vulnerability is traded as CVE-2006-6402 since 12/09/2006. The exploitability is told to be easy. It is possible to launch the attack remotely. The exploitation doesn't require any form of authentication. Technical details are known, but there is no available exploit. This vulnerability is assigned to T1505 by the MITRE ATT&CK project.
It is declared as proof-of-concept. By approaching the search of inurl:mystats.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 databases at OSVDB (30318†), Secunia (SA22813†) and SecurityTracker (ID 1017210†). The entries VDB-33715 and VDB-33713 are related to this item. If you want to get best quality of vulnerability data, you may have to visit VulDB.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.3VulDB Meta Temp Score: 6.9
VulDB Base Score: 7.3
VulDB Temp Score: 6.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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
Physical: No
Local: No
Remote: Yes
Availability: 🔍
Status: Proof-of-Concept
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
11/12/2006 🔍11/12/2006 🔍
11/13/2006 🔍
11/13/2006 🔍
12/09/2006 🔍
12/09/2006 🔍
03/12/2015 🔍
08/10/2018 🔍
Sources
Advisory: vupen.com⛔Status: Not defined
CVE: CVE-2006-6402 (🔍)
GCVE (CVE): GCVE-0-2006-6402
GCVE (VulDB): GCVE-100-33714
Secunia: 22813 - myStats SQL Injection And Cross-Site Scripting Vulnerabilities, Moderately Critical
OSVDB: 30318 - myStats mystats.php details Parameter SQL Injection
SecurityTracker: 1017210
Vupen: ADV-2006-4468
See also: 🔍
Entry
Created: 03/12/2015 22:21Updated: 08/10/2018 06:30
Changes: 03/12/2015 22:21 (50), 08/10/2018 06:30 (8)
Complete: 🔍
Cache ID: 216:CBD: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.