CVE-2008-6180 json
SQL injection vulnerability in system/nlb_user.class.php in NewLife Blogger 3.0 and earlier, and possibly 3.3.1, allows remote attackers to…
published 2009-02-19 17 y ago modified 2026-06-16 4 mo ago also EUVD-2008-6150
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.7%
- EPSS 1.7% chance of exploitation in 30 days, percentile 77%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in system/nlb_user.class.php in NewLife Blogger 3.0 and earlier, and possibly 3.3.1, allows remote attackers to execute arbitrary SQL commands via the nlb3 cookie.
Timeline
- First public exploit (EDB-6739)
- Published
Exploit prediction
1.68% chance of exploitation in the next 30 days, higher than 77% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-6739 NewLife Blogger 3.0 - Insecure Cookie Handling / SQL Injection webapps, 2008-10-12
- securityfocus.com http://www.securityfocus.com/bid/31728 referenced PoC, tagged "exploit" by a source, unverified
- pepelux.org http://www.pepelux.org/exploits/newlife-es.txt 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/6739
exploit
-
securityfocus.com
/bid/31728
vdb-entry, exploit
-
pepelux.org
/exploits/newlife-es.txt
exploit
-
secunia.com
/advisories/32214
third-party-advisory, vendor-advisory
-
vupen.com
/english/advisories/2008/2797
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/45820
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/45821
vdb-entry
-
securityfocus.com
/archive/1/497283/100/0/threaded
mailing-list
Sources
- CVE List CVE-2008-6180
- NVD CVE-2008-6180
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.