CVE-2005-4143 json
SQL injection vulnerability in Lyris ListManager 5.0 through 8.9a allows remote attackers to execute arbitrary SQL commands via SQL code af…
published 2005-12-10 20 y ago modified 2026-06-16 4 mo ago also EUVD-2005-4138
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 72%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in Lyris ListManager 5.0 through 8.9a allows remote attackers to execute arbitrary SQL commands via SQL code after a numeric argument to a /read/attachment URL.
Patch / fix
- osvdb.org/21548 patch
- securityfocus.com/bid/15787 patch
- secunia.com/advisories/17943 advisory
Timeline
- First public exploit (EDB-1366)
- Published
Exploit prediction
1.40% chance of exploitation in the next 30 days, higher than 72% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-1366 Lyris ListManager - Read Message Attachment SQL Injection (Metasploit) remote, 2005-12-09
- osvdb.org http://www.osvdb.org/21548 referenced PoC, tagged "exploit" by a source, unverified
- securityfocus.com http://www.securityfocus.com/bid/15787 referenced PoC, tagged "exploit" by a source, unverified
- metasploit.com http://metasploit.com/research/vulns/lyris_listmanager/ 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 |
References
-
osvdb.org
/21548
vdb-entry, exploit, patch
-
securityfocus.com
/bid/15787
vdb-entry, exploit, patch
-
secunia.com
/advisories/17943
third-party-advisory, patch, vendor-advisory
-
metasploit.com
/research/vulns/lyris_listmanager/
exploit, vendor-advisory
-
securityfocus.com
/archive/1/419077/100/0/threaded
mailing-list
-
vupen.com
/english/advisories/2005/2820
vdb-entry
-
archives.neohapsis.com
/archives/fulldisclosure/2005-12/0349.html
mailing-list
Sources
- CVE List CVE-2005-4143
- NVD CVE-2005-4143
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.