CVE-2009-2361 json
SQL injection vulnerability in include/class.staff.php in osTicket before 1.6 RC5 allows remote attackers to execute arbitrary SQL commands…
published 2009-07-08 17 y ago modified 2026-07-10 4 mo ago also EUVD-2009-2357
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 5.2%
- EPSS 5.2% chance of exploitation in 30 days, percentile 92%
- public exploits
- 1
- Exploit-DB
Summary
SQL injection vulnerability in include/class.staff.php in osTicket before 1.6 RC5 allows remote attackers to execute arbitrary SQL commands via the staff username parameter.
Timeline
- First public exploit (EDB-9032)
- Published
Exploit prediction
5.21% chance of exploitation in the next 30 days, higher than 92% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-9032 osTicket 1.6 RC4 - Admin Login Blind SQL Injection webapps, 2009-06-29
- ngenuity.org http://www.ngenuity.org/wordpress/2009/06/26/osticket-admin-login-blind-sql-injection/ 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/9032
exploit
-
ngenuity.org
/wordpress/2009/06/26/osticket-admin-login-blind-sql-injection/
exploit
-
osticket.com
/forums/project.php?issueid=118
vendor-advisory
-
vupen.com
/english/advisories/2009/1726
vdb-entry, vendor-advisory
-
secunia.com
/advisories/35629
third-party-advisory, vendor-advisory
-
osvdb.org
/55472
vdb-entry
-
securityfocus.com
/archive/1/504615/100/0/threaded
mailing-list
-
securityfocus.com
/bid/35516
vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/51417
vdb-entry
-
securitytracker.com
/id?1022480
vdb-entry
Sources
- CVE List CVE-2009-2361
- NVD CVE-2009-2361
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.