Security readout for executives and security teams
Plain-English summary
GLPI versions before 9.1.5.1 are reported to contain SQL injection in a rules-engine test page. SQL injection can let attackers interfere with application database queries, which may affect confidentiality or integrity. The public bundle does not provide CVSS scoring, authentication requirements, or confirmed exploitation evidence.
Executive priority
Treat this as a priority if GLPI is used for IT service management or asset workflows. The flaw may affect database-backed business records, but the available evidence does not prove active exploitation or provide a severity score.
Technical view
CVE-2017-11475 describes SQL injection in GLPI before 9.1.5.1, specifically in the condition rule field reachable through front/rulesengine.test.php. The provided sources identify the affected version boundary but do not include exploit prerequisites, detailed impact, CVSS metrics, or a named CWE.
Likely exposure
Exposure is most likely in organizations running GLPI versions earlier than 9.1.5.1, especially where the affected rules-engine test route is reachable. The source bundle does not establish whether exploitation requires authentication or special privileges.
Exploitation context
The CVE is not listed as CISA KEV in the provided bundle, and no cited source confirms active exploitation. Public details are limited to the vulnerability description and the GLPI issue reference.
Researcher notes
The source bundle is sparse: it names GLPI before 9.1.5.1 and the affected route and field, but omits CVSS, CWE, exploit prerequisites, and patch notes. Avoid assuming unauthenticated reachability without environment validation.
Mitigation direction
- Inventory GLPI deployments and identify versions earlier than 9.1.5.1.
- Prioritize upgrading affected GLPI instances to a vendor-supported fixed release.
- Check GLPI vendor guidance for any additional mitigation instructions.
- Restrict access to administrative or test routes where operationally feasible.
- Review database and application logs for suspicious activity.
Validation and detection
- Confirm whether any GLPI instance is older than 9.1.5.1.
- Verify whether front/rulesengine.test.php is reachable in deployed environments.
- Review access logs for unusual requests to the affected route.
- Confirm change records show remediation or compensating controls.
- Document any uncertainty around authentication requirements or exposure.
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-11475 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/2476CVE 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.