CVE-2006-0249 json
SQL injection vulnerability in viewcat.php in BitDamaged geoBlog MOD_1.0 allows remote attackers to execute arbitrary SQL commands, then st…
published 2006-01-18 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-0257
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.3%
- EPSS 1.3% chance of exploitation in 30 days, percentile 70%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in viewcat.php in BitDamaged geoBlog MOD_1.0 allows remote attackers to execute arbitrary SQL commands, then steal credentials and upload files, via the cat parameter ($tmpCategory variable).
Timeline
- First public exploit (EDB-27087)
- Published
Exploit prediction
1.29% chance of exploitation in the next 30 days, higher than 70% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-27087 GeoBlog 1.0 - 'viewcat.php' SQL Injection webapps, 2005-01-16
- securityfocus.com http://www.securityfocus.com/bid/16249 referenced PoC, tagged "exploit" by a source, unverified
- evuln.com http://evuln.com/vulns/33/summary.html referenced PoC, tagged "exploit" by a source, unverified
- osvdb.org http://www.osvdb.org/22463 referenced PoC, tagged "exploit" by a source, unverified
- securitytracker.com http://securitytracker.com/id?1015493 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 |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
securityfocus.com
/bid/16249
vdb-entry, exploit
-
evuln.com
/vulns/33/summary.html
exploit
-
osvdb.org
/22463
vdb-entry, exploit
-
securitytracker.com
/id?1015493
vdb-entry, exploit
-
secunia.com
/advisories/18504
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2006/0191
vdb-entry, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/24146
vdb-entry
Sources
- CVE List CVE-2006-0249
- NVD CVE-2006-0249
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.