dbcve.org
GlpiApplication · Glpi Project

CVE-2024-45611

MEDIUM · 5.4 CVSS v3.1 Published 2024-11-15
Fix available
A fix is available. Upgrade to 10.0.17 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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 · unedited
GLPI is an open-source asset and IT management software package that provides ITIL Service Desk features, licenses tracking and software auditing. An authenticated user can bypass the access control policy to create a private RSS feed attached to another user account and use a malicious payload to triggger a stored XSS. Upgrade to 10.0.17.

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 confidence

An authenticated user can bypass GLPI's access control policy to create a private RSS feed attached to another user account. By embedding a malicious payload in the RSS feed, an attacker can trigger stored cross-site scripting (XSS) that executes in the context of the victim user's session.

MitigationUpgrade GLPI to version 10.0.17 or later, which contains the fix for this access control bypass and stored XSS vulnerability.

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
GlpiApplication
Affected:>= 0.84, < 10.0.17

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check GLPI version
    Locate and read the version file (typically version.php or similar in the GLPI root directory) or use the GLPI system information page in the web interface. Compare the installed version number against the affected range: >= 0.84 and < 10.0.17
    Affected if Installed version falls within 0.84 through 10.0.16 inclusive
  2. Verify RSS feed module is enabled
    Access the GLPI administration panel and navigate to Setup > Plugins or Features. Look for RSS feed or Notification configuration. Confirm the RSS feed feature is active in the system
    Affected if RSS feed functionality is enabled and accessible to users
  3. Review user permissions for RSS feed creation
    Navigate to Administration > Profiles in GLPI. Inspect the permissions assigned to standard user profiles, specifically checking if users have the ability to create or manage RSS feeds for other user accounts
    Affected if Standard authenticated users have elevated RSS feed management permissions beyond their own account
  4. Inspect existing RSS feed configurations
    Access the RSS feed management area (typically under Setup > Notifications or a dedicated RSS section). Query the database table storing RSS feed definitions if direct database access is available, looking for feeds owned by users other than the account holder
    Affected if RSS feeds exist that are owned by one user but associated with or visible to other users, indicating a potential access control bypass

A user is affected if running GLPI version 0.84 through 10.0.16 and the RSS feed module is enabled, with standard users having permissions that allow creating feeds attached to other user accounts.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 10.0.17 or later
Fixed in 10.0.17
Interim mitigation

Upgrade GLPI to version 10.0.17 or later, which contains the fix for this access control bypass and stored XSS vulnerability.

Recommended fix High confidence

10.0.17

  1. Backup the existing GLPI installation and database before upgrading
  2. Download GLPI version 10.0.17 from the official GLPI releases (github.com/glpi-project/glpi/releases)
  3. Replace the existing GLPI files with the new version files, preserving the config directory
  4. Run the upgrade process by accessing GLPI through a web browser and following the on-screen prompts
  5. Verify the upgrade was successful by logging in and checking the version number

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Glpi Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45611 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45611 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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