Security readout for executives and security teams
Plain-English summary
This CVE affects GLPI 0.90.4 under a specific database configuration: Big5 Asian encoding. An authenticated remote user could abuse SQL injection flaws to run arbitrary SQL, potentially affecting data confidentiality, integrity, and availability.
Executive priority
Prioritize quickly if GLPI 0.90.4 with Big5 encoding exists in production. The risk is lower if that specific configuration is absent, but public exploit availability justifies prompt validation.
Technical view
The CVE describes multiple SQL injection vulnerabilities in GLPI 0.90.4 triggered by use of a certain character when the database uses Big5 encoding. The attack requires authenticated remote access. The bundle provides no CVSS score, CWE mapping, or confirmed vendor fix details.
Likely exposure
Exposure appears limited to GLPI 0.90.4 deployments using Big5 database encoding and reachable by authenticated users. Systems not running GLPI 0.90.4, or not using Big5 encoding, are not shown as affected by the provided sources.
Exploitation context
A public Exploit-DB reference exists, but the source bundle does not show CISA KEV listing or evidence of active exploitation. Treat this as publicly documented exploitability, not confirmed in-the-wild exploitation.
Researcher notes
Evidence is sparse but specific: authenticated remote SQL injection in GLPI 0.90.4 depends on Big5 database encoding and a character-handling condition. No patch version, CVSS, CWE, or active exploitation evidence is present in the bundle.
Mitigation direction
- Check GLPI vendor guidance and issue 1047 for remediation status.
- Upgrade or retire GLPI 0.90.4 where vendor guidance supports it.
- Restrict GLPI access to trusted authenticated users only.
- Review whether the database uses Big5 encoding.
- Monitor GLPI and database logs for SQL error patterns.
Validation and detection
- Inventory GLPI instances and confirm exact version numbers.
- Verify database character encoding for each GLPI deployment.
- Confirm whether untrusted users can authenticate to GLPI.
- Review logs for unusual SQL errors or data access anomalies.
- Document non-exposure where GLPI 0.90.4 or Big5 is absent.
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-2016-7508 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/1047CVE reference · x_refsource_MISC
- 42262CVE reference · exploit, x_refsource_EXPLOIT-DB
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.