CVE-2022-39323
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. GLPI is a Free Asset and IT Management Software package that provides ITIL Service Desk features, licenses tracking and software auditing. Time based attack using a SQL injection in api REST user_token. This issue has been patched, please upgrade to version 10.0.4. As a workaround, disable login with user_token on API Rest.
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 confidenceA time-based SQL injection vulnerability exists in the GLPI REST API authentication mechanism using user_token. An attacker can exploit this by sending specially crafted requests to the API endpoint, potentially gaining unauthorized access to the database and executing arbitrary SQL commands.
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, < 10.0.4CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Check installed GLPI versionLocate the version.php or version.inc file in your GLPI installation directory, or access the GLPI front page which typically displays the version numberAffected if The installed version is greater than or equal to 9.1 and less than 10.0.4
-
Verify REST API is enabledAccess the GLPI Administration panel, navigate to Setup > General > API, or check the configuration file for 'enable_api' setting set to trueAffected if REST API is enabled and the version is in the affected range
-
Confirm user_token authentication is permittedIn GLPI Administration panel under Setup > General > API, check if the option 'Enable login with user_token' or 'api_user_token' authentication is enabledAffected if User_token based authentication is allowed in the API configuration and the version is in the affected range
You are affected if your GLPI version is 9.1 or higher but below 10.0.4, the REST API is enabled, and user_token authentication is permitted in the API 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.4
Upgrade GLPI to version 10.0.4 or later. As an alternative workaround, disable login with user_token on the REST API configuration.
10.0.4
- 1. Back up your GLPI database and the entire GLPI installation directory
- 2. Back up your configuration file (config_db.php) if upgrading manually
- 3. Download GLPI version 10.0.4 from the official source (glpi-project.org)
- 4. Replace the existing GLPI files with the new version files
- 5. Restore your config_db.php file if performing a manual upgrade
- 6. Run the GLPI upgrade process by accessing the application in a web browser
- 7. Verify that the application functions correctly after upgrade
- 8. If the user_token API login is not needed, consider disabling it in the API settings as an additional security measure
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.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 $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39323 — 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-2022-39323 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