CVE-2006-0238: SQL injection vulnerability in wp-stats.php in GaMerZ WP-Stats 2.0 allows remote attackers to execute arbitrar
CVE-2006-0238 is a high-severity flaw (CVSS 7.5) affecting wp-stats. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
SQL injection vulnerability in wp-stats.php in GaMerZ WP-Stats 2.0 allows remote attackers to execute arbitrary SQL commands via the author parameter.
Why this priority
- High severity
A fixed release or distro patch exists.
Risk facts
| CVSS score | 7.5 (High) |
| EPSS exploit chance | 1.4% (top 27%) |
| CISA exploited list | No |
| Published | 2006-01-18 |
| Last modified | 2026-06-16 |
Last updated 2026-06-16 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2006-0238?
wp-stats: upgrade to newer than 2.0. Exact commands for each OS are on this page.
Is CVE-2006-0238 being exploited?
CVE-2006-0238 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2006-0238 affect?
CVE-2006-0238 affects wp-stats. Severity is high (CVSS 7.5). SQL injection vulnerability in wp-stats.php in GaMerZ WP-Stats 2.0 allows remote attackers to execute arbitrary SQL commands via the author parameter.
How urgent is CVE-2006-0238?
Priority 44/100. High severity
Software pages
Related CVEs
- CVE-2015-10001 MEDIUM 4.3 UPGRADE The WP-Stats WordPress plugin before 2.52 does not have CSRF check when saving its settings, and did not escap