CVE-2023-41326
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 stands for Gestionnaire Libre de Parc Informatique is a Free Asset and IT Management Software package, that provides ITIL Service Desk features, licenses tracking and software auditing. A logged user from any profile can hijack the Kanban feature to alter any user field, and end-up with stealing its account. Users are advised to upgrade to version 10.0.10. There are no known workarounds for this vulnerability.
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 confidenceAn authorization bypass vulnerability in GLPI's Kanban feature allows any authenticated user to modify arbitrary user fields, enabling privilege escalation and account takeover. The flaw permits users from any profile to hijack the Kanban functionality to alter other users' account data.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 9.5.0, < 10.0.10CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Determine installed GLPI versionLocate the GLPI version number in the application (typically visible in the footer of GLPI pages, in a version.php file, or via the Setup > General > General information panel in the web interface)Affected if The installed version is >= 9.5.0 and < 10.0.10
-
Verify Kanban feature is accessibleConfirm that the Kanban functionality is enabled in GLPI. This can be verified by checking if a user can access the Kanban view (typically found in Project or Ticket contexts via the left navigation menu)Affected if The Kanban module or plugin is active and accessible to authenticated users in the environment
-
Confirm user authentication is enabledVerify that GLPI allows user authentication (local or external). The vulnerability requires an authenticated user session to exploit the authorization bypassAffected if The GLPI instance has user authentication enabled and accepts login sessions
A GLPI installation is affected if it runs version 9.5.0 through 10.0.9 and has the Kanban feature accessible to authenticated users, as any logged-in user could exploit the authorization bypass to modify arbitrary user fields.
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 · scoped10.0.10
Upgrade GLPI to version 10.0.10 or later to remediate this vulnerability. No workarounds exist; immediate patching is required.
10.0.10
- Backup your GLPI database and files before starting the upgrade
- Download GLPI version 10.0.10 from the official source (github.com/glpi-project/glpi/releases)
- Replace the existing GLPI files with the new version
- Run the database migration by accessing the GLPI web interface
- Verify the upgrade by logging in and testing that the Kanban feature no longer allows unauthorized user field modifications
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41326 — 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-2023-41326 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