CVE-2024-41678
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 is a free asset and IT management software package. An unauthenticated user can provide a malicious link to a GLPI technician in order to exploit a reflected XSS vulnerability. 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 confidenceA reflected XSS vulnerability in GLPI asset management software allows unauthenticated attackers to craft malicious links containing JavaScript payloads. When a GLPI technician clicks these links, the payload executes in their authenticated browser session, potentially enabling session hijacking or actions on behalf of the victim.
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.50, < 10.0.17CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/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 versionAccess the GLPI login page and look for the version number in the footer, or check the version file typically located at /glpi/version or through the administration panel under Setup > General > General > Application cache and version informationAffected if The displayed version is 0.50 or higher but lower than 10.0.17
-
Verify GLPI is network-accessibleAttempt to access the GLPI web interface from an unauthenticated context (e.g., open the login page URL in a browser)Affected if The GLPI login page loads without requiring authentication, indicating unauthenticated users can reach the application
-
Confirm authenticated session usageRecall that this is a reflected XSS requiring a GLPI technician to click a malicious link while logged in; check whether user education or technical controls prevent clicking untrusted linksAffected if Authenticated GLPI users can click externally-sourced links without warning or filtering, which would allow the reflected XSS to execute in their session
Your environment is affected if the installed GLPI version is 0.50 or higher but lower than 10.0.17 and the application is accessible to unauthenticated users who could trick authenticated technicians into clicking crafted links.
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.17
Upgrade GLPI to version 10.0.17 or later to address this reflected XSS vulnerability. Users should be educated not to click untrusted links, even from seemingly known sources.
10.0.17
- Back up the GLPI database and all files before starting the upgrade
- Download GLPI version 10.0.17 from the official GitHub repository (github.com/glpi-project/glpi/releases) or official distribution channel
- Replace the existing GLPI files with the new version 10.0.17 files
- Run the GLPI upgrade script by accessing /install/update.php through your web browser, or follow the CLI upgrade procedure
- Follow the on-screen prompts to complete the database migration if required
- Verify the upgrade was successful by logging into GLPI and confirming the version shows 10.0.17
- Test the functionality that was previously working to ensure the upgrade did not introduce issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41678 — 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-2024-41678 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