CVE-2008-3845 json
Multiple SQL injection vulnerabilities in Crafty Syntax Live Help (CSLH) 2.14.6 and earlier allow remote attackers to execute arbitrary SQL…
published 2008-08-27 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-3831
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 78%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in Crafty Syntax Live Help (CSLH) 2.14.6 and earlier allow remote attackers to execute arbitrary SQL commands via the department parameter to (1) is_xmlhttp.php and (2) is_flush.php.
Patch / fix
Timeline
- First public exploit (EDB-6307)
- Published
Exploit prediction
1.77% chance of exploitation in the next 30 days, higher than 78% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-6307 Crafty Syntax Live Help 2.14.6 - 'department' SQL Injection webapps, 2008-08-25
- gulftech.org http://www.gulftech.org/?node=research&article_id=00127-08252008 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/30825 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
-
security.craftysyntax.com
/updates/?v=2.14.6
patch
-
exploit-db.com
/exploits/6307
exploit
-
gulftech.org
/?node=research&article_id=00127-08252008
exploit
-
securityfocus.com
/bid/30825
vdb-entry, exploit
-
secunia.com
/advisories/31573
third-party-advisory, vendor-advisory
- sourceforge.net /project/shownotes.php?release_id=620878
-
securityfocus.com
/archive/1/495729/100/0/threaded
mailing-list
-
exchange.xforce.ibmcloud.com
/vulnerabilities/44669
vdb-entry
-
securityreason.com
/securityalert/4192
third-party-advisory
Sources
- CVE List CVE-2008-3845
- NVD CVE-2008-3845
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.