PatchTheCVEmystats vulnerabilities
Recent CVEs affecting mystats products. 3 tracked.
mystats has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2006-12-10. Highest priority: CVE-2006-6402 (score 50/100).
- CVE-2006-6403 MEDIUM 5.0 UPGRADE mystats.php in MyStats 1.0.8 and earlier allows remote attackers to obtain the installation path via (1) detai
- CVE-2006-6402 HIGH 7.5 UPGRADE SQL injection vulnerability in mystats.php in MyStats 1.0.8 and earlier allows remote attackers to execute arb
- CVE-2006-6401 MEDIUM 6.8 UPGRADE Multiple cross-site scripting (XSS) vulnerabilities in mystats.php in MyStats 1.0.8 and earlier allow remote a
FAQ
How do I fix mystats vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is mystats being exploited right now?
None of the tracked mystats CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which mystats CVE should I patch first?
CVE-2006-6402 currently ranks highest (50/100): SQL injection vulnerability in mystats.php in MyStats 1.0.8 and earlier allows remote attackers to execute arb.