CVE-2023-41322
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 user with write access to another user can make requests to change the latter's password and then take control of their account. Users are advised to upgrade to version 10.0.10. There are no known work around 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 · moderate confidenceGLPI versions prior to 10.0.10 contain a vulnerability where an authenticated user with write access to another user's profile can trigger a password change request for that account, leading to unauthorized account takeover. This appears to be an Insecure Direct Object Reference (IDOR) or improper authorization flaw in the user management functionality.
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.1.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.
-
Identify GLPI installation versionLocate the version.php file in the GLPI root directory (e.g., /var/www/glpi/version.php) or check the footer of the GLPI web interface which displays the version numberAffected if The installed version is 9.1.0 or higher but lower than 10.0.10
-
Confirm version is in vulnerable rangeCompare the identified version number against the affected range: any version from 9.1.0 up to but not including 10.0.10 is vulnerableAffected if Version falls within >= 9.1.0 and < 10.0.10
-
Verify user profile write access existsReview GLPI user permissions by accessing Administration > Users > Profile assignment in the web interface, or query the glpi_profiles_users database table to identify users with write permissions to other user accountsAffected if Multiple users exist with write access to profiles beyond their own, enabling the IDOR condition
A GLPI installation is affected if it runs version 9.1.0 or higher but lower than 10.0.10 and allows authenticated users to modify other users profile settings.
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. No workarounds exist for this vulnerability.
10.0.10
- Create a complete backup of the GLPI database and files
- Download GLPI version 10.0.10 from the official source (github.com/GLPI/glpi/releases)
- Put the application in maintenance mode
- Replace the existing GLPI files with the new version 10.0.10 files
- Run the migration script if prompted during first access after file replacement
- Verify that the application is functioning correctly after upgrade
- Disable maintenance mode
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.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 $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-41322 — 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-41322 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