Security readout for executives and security teams
Plain-English summary
GLPI versions before 9.5.3 had an access-control flaw that could let an attacker read records they should not see, including tickets or user data. The business risk is unauthorized disclosure of service desk and identity-related information, but the source bundle does not provide severity scoring or exploitation evidence.
Executive priority
Prioritize remediation where GLPI is internet-facing or contains sensitive operational, customer, or employee data. This is not presented as actively exploited in the bundle, but unauthorized data access can create confidentiality, privacy, and incident-response exposure.
Technical view
CVE-2020-27663 is an IDOR in GLPI's ajax/getDropdownValue.php before version 9.5.3. The CVE description says it allows reading data from any itemType, including Ticket and Users. The bundle does not state authentication requirements, attack complexity, CVSS, CWE, or affected CPEs.
Likely exposure
Exposure is most likely in GLPI deployments running versions earlier than 9.5.3. Risk is higher where GLPI stores sensitive tickets, user records, internal asset details, or customer support information. The provided affected-product metadata is incomplete, so asset teams should verify deployed GLPI versions directly.
Exploitation context
The bundle does not show active exploitation, and KEV is false. The available sources describe a data-read IDOR, not code execution. Authentication requirements and privilege prerequisites are not provided, so treat exploitability details as incomplete until confirmed from GLPI advisory data or internal testing.
Researcher notes
Evidence is limited to the CVE description and GLPI GitHub advisory reference. Key missing details include CVSS, CWE, authentication state, exact vulnerable parameter behavior, and exploit prevalence. Do not assume affected products beyond GLPI before 9.5.3 from the provided sources.
Mitigation direction
- Upgrade GLPI to 9.5.3 or later following vendor guidance.
- Inventory all internet-accessible and internal GLPI instances.
- Restrict GLPI access to trusted networks until remediation is complete.
- Review GLPI logs for unusual access to ajax/getDropdownValue.php.
- Check the GLPI advisory for any additional vendor-specific guidance.
Validation and detection
- Confirm each GLPI instance reports version 9.5.3 or later.
- Identify whether ajax/getDropdownValue.php is reachable on deployed instances.
- Review access logs for unexpected itemType requests or broad record enumeration.
- Verify sensitive ticket and user data access is permission-enforced after upgrade.
- Document any compensating controls for instances awaiting upgrade.
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.
CVE-2020-27663 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/security/advisories/GHSA-pqfv-4pvr-55r4CVE reference · x_refsource_MISC
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.