CVE-2013-2226 json
Multiple SQL injection vulnerabilities in GLPI before 0.83.9 allow remote attackers to execute arbitrary SQL commands via the (1) users_id_…
published 12y ago modified 4mo ago also EUVD-2013-2179
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.7%
- EPSS 2.7% chance of exploitation in 30 days, percentile 85%
- public exploits
- 1
- Exploit-DB
Summary
Multiple SQL injection vulnerabilities in GLPI before 0.83.9 allow remote attackers to execute arbitrary SQL commands via the (1) users_id_assign parameter to ajax/ticketassigninformation.php, (2) filename parameter to front/document.form.php, or (3) table parameter to ajax/comments.php.
Patch / fix
Is CVE-2013-2226 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-26366)
- Published
Exploit prediction
2.69% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-26366 GLPI 0.83.8 - Multiple Vulnerabilities webapps, 2013-06-21
- securityfocus.com http://www.securityfocus.com/bid/60693 referenced PoC, tagged "exploit" by a source, unverified
- zeroscience.mk http://www.zeroscience.mk/en/vulnerabilities/ZSL-2013-5146.php 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
-
glpi-project.org
/spip.php?page=annonce&id_breve=297&lang=en&debut_autres_breves=
patch, vendor-advisory
-
securityfocus.com
/bid/60693
vdb-entry, exploit
-
zeroscience.mk
/en/vulnerabilities/ZSL-2013-5146.php
exploit
Sources
- CVE List CVE-2013-2226
- NVD CVE-2013-2226
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.