Security readout for executives and security teams
Plain-English summary
GLPI versions before 9.1.5 allowed a remote authenticated administrator to delete arbitrary files through the backup page. This is not described as unauthenticated or actively exploited, but it could still cause service disruption or data loss if an admin account is misused or compromised.
Executive priority
Treat as a scheduled but meaningful remediation item. It is not cited as actively exploited, but arbitrary file deletion can affect availability and integrity if administrator access is compromised.
Technical view
The flaw is in GLPI `front/backup.php` before 9.1.5. A crafted `file` parameter could let an authenticated administrator delete files outside the intended backup workflow. No CVSS, CWE, or KEV evidence is provided in the source bundle.
Likely exposure
Exposure is limited to GLPI deployments older than 9.1.5 where an attacker has administrator authentication or can abuse an administrator session.
Exploitation context
The provided sources do not show active exploitation. The attack requires authenticated administrator privileges, making it most relevant after credential theft, session compromise, malicious insider activity, or chained compromise.
Researcher notes
Evidence is narrow but consistent: the CVE description identifies `front/backup.php`, GLPI before 9.1.5, authenticated administrators, and arbitrary file deletion via a crafted `file` parameter. No public CVSS, CWE, or exploit-status signal is provided.
Mitigation direction
- Upgrade GLPI to version 9.1.5 or later.
- Review GLPI vendor release notes and guidance before remediation.
- Restrict GLPI administrator access to trusted users and networks.
- Audit administrator accounts for stale, shared, or weakly protected access.
- Ensure current backups exist before upgrading or changing access controls.
Validation and detection
- Inventory GLPI instances and record their exact versions.
- Flag any GLPI deployment older than 9.1.5.
- Review web and application logs for unusual backup-page administrator activity.
- Confirm only authorized administrators can access backup functionality.
- Verify remediation in a staging or maintenance window where practical.
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-2017-11183 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/2450CVE reference · x_refsource_CONFIRM
- https://github.com/glpi-project/glpi/releases/tag/9.1.5CVE 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.