CVE-2008-1895 json
Multiple SQL injection vulnerabilities in Carbon Communities 2.4 and earlier allow remote attackers to execute arbitrary SQL commands via t…
published 2008-04-18 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-1895
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.2%
- EPSS 1.2% chance of exploitation in 30 days, percentile 68%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in Carbon Communities 2.4 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) ID parameter to events.asp, the (2) UserName parameter to getpassword.asp, and possibly an unspecified parameter to (3) option_Update.asp in an edit action.
Timeline
- First public exploit (EDB-5456)
- Published
Exploit prediction
1.19% chance of exploitation in the next 30 days, higher than 68% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-5456 Carbon Communities 2.4 - Multiple Vulnerabilities webapps, 2008-04-16
- bugreport.ir http://bugreport.ir/index.php?/35 referenced PoC, tagged "exploit" by a source, unverified
- bugreport.ir http://bugreport.ir/index.php?/35/exploit referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/28806 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/5456
exploit
-
bugreport.ir
/index.php?/35
exploit
-
bugreport.ir
/index.php?/35/exploit
exploit
-
securityfocus.com
/bid/28806
vdb-entry, exploit
-
secunia.com
/advisories/29827
third-party-advisory, vendor-advisory
-
securityfocus.com
/archive/1/490923/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/41845
vdb-entry
Sources
- CVE List CVE-2008-1895
- NVD CVE-2008-1895
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.