CVE-2022-39372
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. Authenticated users may store malicious code in their account information. This issue has been patched, please upgrade to version 10.0.4. There are currently no known workarounds.
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 confidenceAuthenticated GLPI users can inject malicious code (stored XSS) into their account information fields due to insufficient input validation/sanitization. This allows script execution in browsers of other users viewing the affected 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>= 0.70, < 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
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 GLPI version in application footerLog into GLPI and look at the version number displayed in the page footer, or access the General Setup page where the version is typically shownAffected if The displayed version is 0.70 or higher but lower than 10.0.4
-
Check GLPI version via config fileLocate the GLPI installation directory and check the version file (such as version.txt or config/Config.php) for the installed version numberAffected if The version in the config file matches the affected range >= 0.70 and < 10.0.4
-
Verify user authentication is enabledConfirm that GLPI user authentication is active (typical default state) by checking if login is required to access the applicationAffected if Anonymous or unauthenticated access is allowed without any authentication barrier
-
Confirm account profile feature is accessibleCheck if authenticated users can access and edit their own profile or personal information section (typically found under Setup > Personal > Preferences or User menu)Affected if Users have the ability to modify their account information fields where the XSS payload could be injected
Your environment is affected if the installed GLPI version is 0.70 or higher but below 10.0.4 and user authentication is enabled, allowing authenticated users to inject scripts into their profile fields that will execute when viewed by other users.
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. No workarounds are available.
10.0.4
- Backup your GLPI database and all application files before proceeding with the upgrade
- Download GLPI version 10.0.4 from the official GLPI repository or distribution site
- Follow the standard GLPI upgrade procedure: extract the new version files, ensure configuration files are preserved, and run the migration scripts if needed
- Verify the upgrade was successful by logging in and checking that the application functions correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39372 — 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-39372 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