CVE-2006-1639: SQL injection vulnerability in index.php in wpBlog 0.4 allows remote attackers to execute arbitrary SQL comman
CVE-2006-1639 is a medium-severity flaw (CVSS 5.1) affecting wpblog. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
SQL injection vulnerability in index.php in wpBlog 0.4 allows remote attackers to execute arbitrary SQL commands via the postid parameter.
Why this priority
- No elevated risk signals yet
No fix is published yet: follow the downgrade or mitigation steps.
Risk facts
| CVSS score | 5.1 (Medium) |
| EPSS exploit chance | 1.6% (top 24%) |
| CISA exploited list | No |
| Published | 2006-04-06 |
| 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-1639?
wpblog: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.
Is CVE-2006-1639 being exploited?
CVE-2006-1639 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-1639 affect?
CVE-2006-1639 affects wpblog. Severity is medium (CVSS 5.1). SQL injection vulnerability in index.php in wpBlog 0.4 allows remote attackers to execute arbitrary SQL commands via the postid parameter.
How urgent is CVE-2006-1639?
Priority 37/100. No elevated risk signals yet.