CVE-2010-5009 json
SQL injection vulnerability in index.php in UTStats Beta 4 and earlier allows remote attackers to execute arbitrary SQL commands via the pi…
published 15y ago modified 4mo ago also EUVD-2010-4973
- 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
SQL injection vulnerability in index.php in UTStats Beta 4 and earlier allows remote attackers to execute arbitrary SQL commands via the pid parameter in a matchp action.
Is CVE-2010-5009 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-13854)
- Published
Exploit prediction
1.15% chance of exploitation in the next 30 days, higher than 67% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-13854 UTStats - Cross-Site Scripting / SQL Injection / Full Path Disclosure webapps, 2010-06-13
- securityfocus.com http://www.securityfocus.com/bid/40836 referenced PoC, tagged "exploit" by a source, unverified
- packetstormsecurity.org http://packetstormsecurity.org/1006-exploits/utstats-sqlxss.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/13854
exploit
-
securityfocus.com
/bid/40836
vdb-entry, exploit
-
packetstormsecurity.org
/1006-exploits/utstats-sqlxss.txt
exploit
-
vupen.com
/english/advisories/2010/1465
vdb-entry, vendor-advisory
-
securityreason.com
/securityalert/8506
third-party-advisory
-
exchange.xforce.ibmcloud.com
/vulnerabilities/59402
vdb-entry
Sources
- CVE List CVE-2010-5009
- NVD CVE-2010-5009
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.