CVE-2026-42317
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedGLPI is a free asset and IT management software package. Starting in version 0.78 and prior to versions 10.0.25 and 11.0.7, a technician can delete arbitrary files from the filesystem as long as the webserver has write rights on them. Upgrade to 10.0.25 or 11.0.7 to receive a patch.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceGLPI contains an arbitrary file deletion vulnerability allowing authenticated technicians to delete arbitrary files on the filesystem where the webserver has write permissions. The vulnerability stems from improper authorization or path validation in the application.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- Authentication
- X
- User interaction
- None
- Scope
- X
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify GLPI versionLocate the version file in your GLPI installation (typically in the root directory or config folder) and read the version numberAffected if version is 0.78 through 10.0.x before 10.0.25, or 11.x before 11.0.7
-
Verify technician accounts existCheck if any user accounts with technician profile exist in the GLPI user database (glpi_users table with profile linking to technician role)Affected if technician-level accounts are present in the system
-
Check webserver write permissionsReview filesystem permissions to determine if the webserver process user has write access to directories outside the GLPI application folderAffected if webserver user has write permissions to arbitrary filesystem locations
-
Identify file deletion featureLocate and examine the file deletion functionality in GLPI (typically in ticket follow-ups, documents, or attachment handling modules)Affected if the document/attachment deletion feature is accessible to technician-level users
Your environment is affected if GLPI version is 0.78 through 10.0.x before 10.0.25 or 11.x before 11.0.7, technician accounts exist, and the webserver process has write access to files outside the GLPI directory.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade GLPI to version 10.0.25 or 11.0.7 to receive the patch that addresses the arbitrary file deletion vulnerability.
10.0.25 or 11.0.7
- Backup the GLPI database and all files before proceeding with the upgrade
- Verify the current installed version matches the affected range (0.78 through versions prior to 10.0.25 or 11.0.7)
- Review the official GLPI upgrade documentation for your current version
- Download GLPI version 10.0.25 or version 11.0.7 from the official GLPI repository or website
- Test the upgrade in a staging environment before applying to production
- Execute the upgrade following the documented upgrade procedure
- Verify the fix is applied by confirming the technician role can no longer delete arbitrary files outside allowed directories
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-42317 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-42317 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data