Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HSummary
CVE-2022-31061 is a critical-severity SQL Injection (CWE-89) vulnerability in Glpi-Project Glpi. Its CVSS base score is 9.8 (Critical).
Operationally, ranked in the top 1% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
GLPI, an open-source IT asset management and service desk platform, contains a SQL injection vulnerability (CWE-89) on its unauthenticated login page in affected versions. The flaw permits direct database manipulation without any credentials and carries a CVSS 3.1 score of 9.8, reflecting network-exploitable impact on confidentiality, integrity, and availability.
An attacker can submit crafted input through the login form to execute arbitrary SQL queries, potentially extracting sensitive data, modifying records, or gaining administrative control over the GLPI instance and its underlying database. No prior authentication or user interaction is required, making the issue remotely exploitable by any network-reachable adversary.
The project’s security advisory and associated commits instruct administrators to upgrade immediately to a patched release; no workarounds are documented. The referenced GitHub advisory (GHSA-w2gc-v2gm-q7wq) and fix commit (21ae07d) contain the remediation details.
EPSS for the CVE rose from a low post-disclosure baseline to a peak of 0.5177 in late 2025 before receding to the current value of 0.4591, indicating renewed exploitation interest well after the original 2022 publication.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2022-52733
Vulnerability Data
GLPI is a Free Asset and IT Management Software package, Data center management, ITIL Service Desk, licenses tracking and software auditing. In affected versions there is a SQL injection vulnerability which is possible on login page. No user credentials are…
more
required to exploit this vulnerability. Users are advised to upgrade as soon as possible. There are no known workarounds for this issue.
- CWE(s)
Related Threats
Likely ATT&CK TechniquesAI
Techniques this vulnerability likely enables, inferred from its description, weakness type, and attributed-actor tradecraft. Confidence is per-technique.
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Mandatory validation/sanitization of all unauthenticated login-form inputs would have blocked the crafted SQL payloads that constitute the CVE-2022-31061 attack.
Requires prompt application of the vendor-supplied patch (the only remediation stated in the advisory) that eliminates the SQL-injection flaw on the login page.
Integrity verification of the GLPI application code and configuration can detect unauthorized post-exploitation modifications resulting from successful SQL injection.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly target injection flaws during coding and review so largely prevent CWE-89 introduction, yet the single broad outcome leaves residual risk from incomplete neutralization techniques or missed edge cases.
Training raises developer awareness of SQLi risks and can reduce introduction likelihood (partial) but removes none of the actual coding flaw's risk by itself since technical neutralization is still required.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
The same secure-coding and static-analysis activities surface missing neutralization of SQL metacharacters before the system is accepted.
Early warnings and shared best-practice information help organizations apply the latest remediation techniques against SQL-injection vulnerabilities.
Threat-intelligence feeds that surface new SQL-injection campaigns enable rapid updates to query-construction defenses and detection signatures before exploitation occurs.
Secure-coding rules and security testing phases mandate the use of parameterized queries or equivalent escaping, preventing the construction of dynamic SQL statements from untrusted input.
Language-specific secure coding rules, peer review and SAST together prevent the construction of SQL statements from untrusted data without proper parameterization or escaping.