CVE-2008-7075 json
Multiple SQL injection vulnerabilities in Kalptaru Infotech Ltd.
published 2009-08-25 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-7034
- 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
Multiple SQL injection vulnerabilities in Kalptaru Infotech Ltd. Star Articles 6.0 allow remote attackers to inject arbitrary SQL commands via (1) the subcatid parameter to article.list.php; or the artid parameter to (2) article.print.php, (3) article.comments.php, (4) article.publisher.php, or (5) article.download.php; and (6) the PATH_INFO to article.download.php. NOTE: some of these details are obtained from third party information.
Timeline
- First public exploit (EDB-7240)
- Published
Exploit prediction
2.03% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-7243 Star Articles 6.0 - Blind SQL Injection (2) webapps, 2008-11-27
- EDB-7240 Star Articles 6.0 - Blind SQL Injection (1) webapps, 2008-11-26
- securityfocus.com http://www.securityfocus.com/bid/32489 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/7240
exploit
-
exploit-db.com
/exploits/7243
exploit
-
securityfocus.com
/bid/32489
vdb-entry, exploit
-
vupen.com
/english/advisories/2008/3269
vdb-entry, vendor-advisory
-
secunia.com
/advisories/32887
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/46981
vdb-entry
-
osvdb.org
/50455
vdb-entry
-
osvdb.org
/50453
vdb-entry
-
osvdb.org
/50454
vdb-entry
-
osvdb.org
/50452
vdb-entry
-
osvdb.org
/50456
vdb-entry
Sources
- CVE List CVE-2008-7075
- NVD CVE-2008-7075
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.