CVE-2023-42802
Glpi-Project Glpi 10.0.7 – 10.0.10
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-42802 is a critical-severity Improper Input Validation (CWE-20) vulnerability in Glpi-Project Glpi. Its CVSS base score is 10.0 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Data Obfuscation (T1001); ranked in the top 36% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
GLPI, an open-source IT asset management application, contains an unverified object instantiation flaw in versions 10.0.7 through 10.0.9. The issue permits an attacker to upload arbitrary PHP files into directories outside the intended upload locations, which can result in remote code execution when the web server subsequently processes those files, depending on server configuration and available PHP libraries.
An unauthenticated remote attacker can exploit the vulnerability over the network without user interaction to place and invoke malicious PHP code, achieving full compromise of the confidentiality, integrity, and availability of the affected GLPI instance. The CVSS 3.1 base score of 10.0 reflects the absence of required authentication and the scope change that allows the attacker to impact resources beyond the vulnerable component.
The official fix is included in GLPI 10.0.10, as noted in the project’s GitHub release notes and the accompanying security advisory GHSA-rrh2-x4ch-pq3m. As an interim mitigation, administrators can revoke write permissions on the /ajax and /front paths for the web-server user. The associated EPSS score has remained flat at 0.0616 with no material increase since disclosure.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-47229
Vulnerability Data
GLPI is a free asset and IT management software package. Starting in version 10.0.7 and prior to version 10.0.10, an unverified object instantiation allows one to upload malicious PHP files to unwanted directories. Depending on web server configuration and available…
more
system libraries, malicious PHP files can then be executed through a web server request. Version 10.0.10 fixes this issue. As a workaround, remove write access on `/ajax` and `/front` files to the web server.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V5.1.1
Likely Mitigating Controls AI
Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Requiring identifiable owners for portable devices reduces the attack surface for unrestricted uploads of dangerous file types via anonymous media.
Security testing and developer training directly verify and enforce proper input validation, reducing exploitability of injection and malformed-data weaknesses.
Security testing and evaluation at multiple SDLC stages directly detects missing or flawed input validation, with the required remediation process ensuring fixes are applied.
Dangerous file uploads can be detonated in the chamber to determine malice before any production write or execution occurs.
Prevents unrestricted writing of arbitrary or malicious firmware by keeping hardware write-protect enabled except under tightly controlled manual procedures.
Directly implements checks on information inputs to reject invalid data before processing.
Scans files from external sources on download/open/execute, blocking unrestricted uploads of dangerous file types.
Spam protection mechanisms perform filtering and detection on inbound/outbound messages, directly compensating for missing or weak input validation of unsolicited content.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Hardened configuration baselines can enforce allowed file types and processing rules.
Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.
Secure development practices include input validation and file-type restrictions that prevent this weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Hardening callouts derived
DISA STIG baselines are authored against specific weaknesses. Where this CVE cites a broad weakness class, the mapping is not asserted at that abstraction (owner ruling, 2026-09-25: grade only at Base and below), so no rule is shown here rather than a rule shown against the wrong grain.
- No fine-grained STIG row for CWE-20, a class-level weakness, and none of its children carries one either.