CVE-2022-39375
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. Users may be able to create a public RSS feed to inject malicious code in dashboards of other users. 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 confidenceGLPI versions prior to 10.0.4 contain a stored Cross-Site Scripting (XSS) vulnerability where authenticated users can create public RSS feeds containing malicious JavaScript code. When other users view these RSS feeds in their dashboards, the injected script executes, potentially allowing session hijacking or unauthorized actions.
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.84, < 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.
-
Determine installed GLPI versionLog into the GLPI dashboard and check the version number typically displayed in the footer or under Setup > General > System Information. Alternatively, inspect the version field in the config/config.php file or the chkfile of the GLPI root directory.Affected if The installed version is 0.84 or higher but lower than 10.0.4
-
Verify RSS feed feature is enabledNavigate to Setup > General > Features or Setup > dropdown and check if the RSS feed or External Feeds feature is turned on. This is typically found under the 'Features' or 'External links' settings.Affected if RSS feeds are enabled in the GLPI configuration
-
Confirm public RSS feed creation is permittedGo to Setup > RSS Feed > Create or check the rights assigned to user roles under Administration > Profiles. Look for permission to create public RSS feeds that are visible to other users.Affected if Authenticated users have permission to create public or shared RSS feeds visible to other users
-
Check for existing malicious RSS feedsNavigate to Tools > RSS Feed or the RSS feed management section. Review any existing RSS feeds for suspicious content, unusual URLs, or JavaScript code in the feed name, URL, or description fields.Affected if Any RSS feed exists that contains script tags, javascript: URIs, or other XSS payloads in its name, URL, or content fields
-
Inspect dashboard RSS feed widgetsView the personal or central dashboard as a non-admin user. Look for any RSS feed widgets that display external content and check if they load from untrusted sources.Affected if RSS feed widgets are present on user dashboards and can display content from external URLs
A user is affected if their GLPI version is 0.84 through 10.0.3 inclusive, the RSS feed feature is enabled, and users have the ability to create or view shared RSS feeds on dashboards.
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 to patch this vulnerability. No workarounds are available.
10.0.4
- 1. Backup your GLPI database and files before upgrading
- 2. Download GLPI version 10.0.4 from the official GitHub releases or GLPI website
- 3. Extract the new version files to your web server document root
- 4. Copy your existing configuration file (config_db.php) to the new installation
- 5. Run the migration script if prompted by accessing the GLPI URL in a web browser
- 6. Clear any caches if applicable
- 7. Verify the installation by logging in and checking that RSS feed functionality works correctly
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2022-39375 — 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-39375 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