CVE-2009-4795 json
Multiple SQL injection vulnerabilities in Xlight FTP Server before 3.2.1, when ODBC authentication is enabled, allow remote attackers to ex…
published 16y ago modified 4mo ago also EUVD-2009-4758
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.0%
- EPSS 2.0% chance of exploitation in 30 days, percentile 81%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in Xlight FTP Server before 3.2.1, when ODBC authentication is enabled, allow remote attackers to execute arbitrary SQL commands via the (1) USER (aka username) or (2) PASS (aka password) command.
Patch / fix
Is CVE-2009-4795 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerTimeline
- First public exploit (EDB-32877)
- Published
Exploit prediction
2.03% chance of exploitation in the next 30 days, higher than 81% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-32877 Xlight FTP Server 3.2 - 'user' SQL Injection remote, 2009-03-19
- securityfocus.com http://www.securityfocus.com/bid/34288 referenced PoC, tagged "exploit" by a source, unverified
- xlightftpd.com http://www.xlightftpd.com/forum/viewtopic.php?t=1042 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
securityfocus.com
/bid/34288
vdb-entry, exploit, patch
-
xlightftpd.com
/forum/viewtopic.php?t=1042
exploit
-
secunia.com
/advisories/34513
third-party-advisory, vendor-advisory
- xlightftpd.com /whatsnew.htm
-
exchange.xforce.ibmcloud.com
/vulnerabilities/49495
vdb-entry
Sources
- CVE List CVE-2009-4795
- NVD CVE-2009-4795
Fencer Intel 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.