dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-42318

HIGH · 7.0 CVSS v4.0 Published 2026-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
76/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
GLPI is a free asset and IT management software package. Starting in version 9.5.0 and prior to versions 10.0.25 and 11.0.7, low privilege users with access to planning can delete any object in GLPI. Upgrade to 11.0.7 or 10.0.25 to receive a patch. As a workaround, disable delete rights for User's planning.

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 · high confidence

GLPI contains a broken access control vulnerability where low-privilege users with planning access can delete any object in the system, regardless of their intended permissions. This is an Insecure Direct Object Reference (IDOR) or authorization bypass affecting the planning module.

MitigationUpgrade to GLPI version 10.0.25 or 11.0.7 to receive the patch. Alternatively, as a temporary workaround, disable delete rights for User's planning in the permission settings.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify GLPI version
    Locate the version file or access the GLPI installation directory and check the version number (typically in files like VERSION, config.php, or via the GLPI system information page in the web interface)
    Affected if The installed version falls within 9.5.0-10.0.24 or equals 11.0.6
  2. Confirm planning module is enabled
    Access GLPI administration panel, navigate to Setup > Plugins or Setup > Dropdowns to verify if the Planning (or Calendar/Planning) module is active and installed
    Affected if The Planning module is enabled and accessible to users
  3. Verify user planning permissions
    Go to Administration > Profiles > select a low-privilege profile > check the Planning permission section to see if any planning-related access rights are granted to non-administrative users
    Affected if Low-privilege users (e.g., Self-Service, Observer roles) have any planning access or permissions granted
  4. Test object deletion scope
    Using a low-privilege account with only planning access, attempt to delete an object outside the planning domain (e.g., a ticket, document, or inventory item the user should not own or have rights to) to confirm the IDOR condition
    Affected if A user with only planning permissions can successfully delete objects they should not have permission to delete

A user is affected if their GLPI version is 9.5.0-10.0.24 or 11.0.6 AND the Planning module is enabled with any access granted to low-privilege users, allowing unauthorized deletion of objects.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to GLPI version 10.0.25 or 11.0.7 to receive the patch. Alternatively, as a temporary workaround, disable delete rights for User's planning in the permission settings.

Recommended fix High confidence

Upgrade to GLPI 10.0.25 or 11.0.7 (whichever matches your current major version branch)

  1. 1. Identify the current GLPI version by checking the version file or administration interface
  2. 2. Backup the GLPI database and all files before proceeding with the upgrade
  3. 3. Download the appropriate fixed version (10.0.25 or 11.0.7) from the official GLPI repository
  4. 4. Replace the existing GLPI files with the new version files, preserving the config directory
  5. 5. Run the GLPI upgrade process by accessing the installation URL
  6. 6. Verify the upgrade was successful by logging in and checking the version
  7. 7. Test that planning functionality works and the authorization fix is applied

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-42318 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-42318 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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