CVE-2006-0324 json
SQL injection vulnerability in WebspotBlogging 3.0 allows remote attackers to execute arbitrary SQL commands and bypass authentication via…
published 2006-01-19 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-0331
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.6%
- EPSS 2.6% chance of exploitation in 30 days, percentile 85%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in WebspotBlogging 3.0 allows remote attackers to execute arbitrary SQL commands and bypass authentication via the username parameter to login.php.
Timeline
- First public exploit (EDB-27114)
- Published
Exploit prediction
2.57% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-27114 WebspotBlogging 3.0 - 'login.php' SQL Injection webapps, 2006-01-19
- securityfocus.com http://www.securityfocus.com/bid/16319 referenced PoC, tagged "exploit" by a source, unverified
- evuln.com http://evuln.com/vulns/41/summary.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
References
-
securityfocus.com
/bid/16319
vdb-entry, exploit
-
evuln.com
/vulns/41/summary.html
exploit, vendor-advisory
-
secunia.com
/advisories/18560
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24222
vdb-entry
- sourceforge.net /project/shownotes.php?release_id=387180&group_id=156586
-
securitytracker.com
/id?1015522
vdb-entry
- sourceforge.net /forum/forum.php?forum_id=532233
-
securityfocus.com
/archive/1/422364/100/0/threaded
mailing-list
-
vupen.com
/english/advisories/2006/0268
vdb-entry
-
osvdb.org
/22670
vdb-entry
-
securityreason.com
/securityalert/356
third-party-advisory
Sources
- CVE List CVE-2006-0324
- NVD CVE-2006-0324
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.