CVE-2008-3491 json
SQL injection vulnerability in go.php in Scripts24 iPost 1.0.1 and iTGP 1.0.4 allows remote attackers to execute arbitrary SQL commands via…
published 2008-08-06 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3477
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 2
- Exploit-DB
Summary
SQL injection vulnerability in go.php in Scripts24 iPost 1.0.1 and iTGP 1.0.4 allows remote attackers to execute arbitrary SQL commands via the id parameter in a report action.
Timeline
- First public exploit (EDB-6186)
- Published
Exploit prediction
2.02% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-6186 Scripts24 iPost 1.0.1 - 'id' SQL Injection webapps, 2008-08-01
- EDB-6185 Scripts24 iTGP 1.0.4 - 'id' SQL Injection webapps, 2008-08-01
- securityfocus.com http://www.securityfocus.com/bid/30505 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/30504 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
-
exploit-db.com
/exploits/6185
exploit
-
exploit-db.com
/exploits/6186
exploit
-
securityfocus.com
/bid/30505
vdb-entry, exploit
-
securityfocus.com
/bid/30504
vdb-entry, exploit
-
osvdb.org
/47333
vdb-entry
-
secunia.com
/advisories/31344
third-party-advisory
-
securityreason.com
/securityalert/4117
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/44175
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/44176
vdb-entry
-
secunia.com
/advisories/31345
third-party-advisory
Sources
- CVE List CVE-2008-3491
- NVD CVE-2008-3491
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.