dbcve.org
Missing AuthorizationWeakness · CWE-862

CVE-2026-44281

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 0.78 and prior to versions 10.0.25 and 11.0.7, an authenticated user with config READ permission can read a specific asset object. Upgrade to 11.0.7 or 10.0.25 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 · high confidence

This is an information disclosure vulnerability in GLPI asset management software where an authenticated user with only config READ permission can access specific asset objects they should not be authorized to view. The vulnerability stems from improper access control enforcement allowing privilege escalation through read access.

MitigationUpgrade GLPI to version 10.0.25 or 11.0.7 as specified in the official advisory. This is a standard application patch requiring no custom code changes.

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. Confirm GLPI installation
    Look for GLPI web application files in the web server document root (e.g., /var/www/html/glpi, /www/glpi, or the equivalent path for your web server). Check for the presence of index.php, ajax, or front directories with GLPI-specific files.
    Affected if GLPI is installed and accessible via web or file system
  2. Identify installed GLPI version
    Check the GLPI version by viewing the version file at inc/checksetup.php or looking at the footer of the GLPI login page. Alternatively, access the general setup page when logged in to view the version number.
    Affected if Unable to determine version or version is below 10.0.25 or 11.0.7
  3. Compare version against affected ranges
    Compare your installed version to the fixed versions: GLPI 10.x versions below 10.0.25 are affected; GLPI 11.x versions below 11.0.7 are affected. Any version below these thresholds contains the vulnerability.
    Affected if Installed version is 10.0.x below 10.0.25 OR 11.0.x below 11.0.7
  4. Verify user permission model exists
    Confirm that GLPI user authentication and the permission system are active. The vulnerability exploits users with only 'config READ' permission accessing asset objects. Check if user roles and profiles are configured in the GLPI administration panel.
    Affected if GLPI has active user accounts with assigned profiles containing 'config READ' permission

The environment is affected if GLPI is installed with a version below 10.0.25 (for 10.x branch) or below 11.0.7 (for 11.x branch) and has authenticated users with the 'config READ' permission enabled.

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 GLPI to version 10.0.25 or 11.0.7 as specified in the official advisory. This is a standard application patch requiring no custom code changes.

Recommended fix High confidence

GLPI 10.0.25 or GLPI 11.0.7

  1. Back up the current GLPI installation and database before upgrading
  2. Download GLPI version 10.0.25 or version 11.0.7 from the official GitHub repository or release page
  3. Follow the official GLPI upgrade documentation to apply the update
  4. Verify the upgrade was successful and test that the authorization controls now properly restrict asset object access
Caveat Review release notes for any breaking changes between your current version and the target upgrade version

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44281 — 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-44281 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