CVE-2008-1496 json
Multiple SQL injection vulnerabilities in PEEL, possibly 3.x and earlier, allow remote attackers to execute arbitrary SQL commands via the…
published 2008-03-25 18 y ago modified 2026-06-16 4 mo ago also EUVD-2008-1498
- 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 67%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in PEEL, possibly 3.x and earlier, allow remote attackers to execute arbitrary SQL commands via the (1) email parameter to (a) membre.php, and the (2) timestamp parameter to (b) the details action in achat/historique_commandes.php and (c) the facture action in factures/facture_html.php.
Timeline
- First public exploit (EDB-5281)
- Published
Exploit prediction
1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-5281 PEEL CMS 3.x - Admin Hash Extraction / Arbitrary File Upload webapps, 2008-03-19
- securityfocus.com http://www.securityfocus.com/bid/28346 referenced PoC, tagged "exploit" by a source, unverified
- realn.free.fr http://realn.free.fr/releases/70207 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/5281
exploit
-
securityfocus.com
/bid/28346
vdb-entry, exploit
-
realn.free.fr
/releases/70207
exploit
-
secunia.com
/advisories/29466
third-party-advisory, vendor-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/41341
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/41353
vdb-entry
Sources
- CVE List CVE-2008-1496
- NVD CVE-2008-1496
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.