Security readout for executives and security teams
Plain-English summary
GLPI versions before 9.1.5.1 contain a SQL injection flaw in a software-version component reachable through an AJAX endpoint. For organizations using GLPI to manage IT assets, compromise could expose sensitive inventory or operational data. The provided sources do not confirm active exploitation.
Executive priority
Prioritize remediation for internet-accessible or broadly accessible GLPI systems. Asset management platforms often hold valuable operational data, and SQL injection is a serious class even without confirmed exploitation evidence here.
Technical view
CVE-2017-11474 is a SQL injection in the $crit variable in inc/computer_softwareversion.class.php, reportedly reachable via ajax/common.tabs.php. The affected product is GLPI before 9.1.5.1. The bundle provides no CVSS, CWE, authentication context, or proof-of-exploitation details.
Likely exposure
Exposure is most likely where GLPI deployments are older than 9.1.5.1, especially if the GLPI web interface is reachable by untrusted users. The provided sources do not establish affected CPEs or whether authentication is required.
Exploitation context
The source bundle names an injectable variable and web route but does not include exploit code, observed attacks, or KEV listing. Treat this as a plausible application-layer database risk, not as confirmed active exploitation.
Researcher notes
Evidence is limited to the CVE description and the GLPI GitHub issue reference. Do not assume authentication requirements, database impact, or exploit maturity without reviewing the upstream issue and local application behavior.
Mitigation direction
- Upgrade GLPI to 9.1.5.1 or later where feasible.
- Check GLPI project guidance and issue 2475 for vendor-specific remediation context.
- Restrict access to GLPI administration interfaces to trusted networks and users.
- Review database and application logs for suspicious requests to ajax/common.tabs.php.
Validation and detection
- Inventory GLPI instances and confirm exact running versions.
- Flag any GLPI deployment older than 9.1.5.1 as affected.
- Confirm whether ajax/common.tabs.php is reachable from untrusted network paths.
- Review GLPI logs around July 2017 onward for unusual software-version tab activity.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
Database behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2017-11474 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/glpi-project/glpi/issues/2475CVE reference · x_refsource_CONFIRM
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.