dbcve.org
GlpiApplication · Glpi Project

CVE-2024-43418

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

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 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 · high confidence

GLPI versions before 10.0.17 contain a reflected cross-site scripting (XSS) vulnerability. An unauthenticated attacker can craft a malicious URL containing JavaScript payload and trick a GLPI technician into clicking it. The payload reflects back in the response, executing in the technician's browser context.

MitigationUpgrade GLPI to version 10.0.17 or later. Until upgrade is possible, disable or sanitize URL parameters in GLPI endpoints and train users to avoid clicking untrusted links.

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.65, < 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
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 checks

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

  1. Locate GLPI version file
    Access the GLPI installation directory and locate the version file, typically found in files/._glpi_version, config/config.php, or the version constant defined in the source code. Alternatively, check the footer of any GLPI login or dashboard page which often displays the version number.
    Affected if The displayed version is 10.0.x where x is less than 17, or any version between 0.65 and 10.0.0.
  2. Compare installed version to affected range
    Review the identified version number and compare it against the affected range: version 0.65 or higher but lower than 10.0.17. GLPI versions follow semantic versioning where the first number is major, second is minor, third is patch.
    Affected if The installed version falls within >= 0.65 and < 10.0.17.
  3. Identify URL parameter handling
    Examine GLPI endpoints that process URL parameters without sanitization. Common entry points include search filters, redirect parameters, or any endpoint that echoes back query string values in the HTML response. Check the HTTP response when passing special characters like <script> in URL parameters.
    Affected if The application reflects unsanitized URL parameters in its HTTP response without proper encoding or validation.
  4. Verify technician access exposure
    Determine if the GLPI instance is accessible to unauthenticated users or if technician accounts exist that could be targeted. Check if the login page and any public-facing GLPI endpoints accept URL parameters that could be manipulated.
    Affected if Technician users can access GLPI and click on externally-supplied URLs, making them vulnerable to reflected XSS attacks via malicious links.

If the installed GLPI version is 0.65 or higher but lower than 10.0.17, and the application reflects URL parameters in responses without sanitization, the environment is affected by this reflected XSS vulnerability.

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. Until upgrade is possible, disable or sanitize URL parameters in GLPI endpoints and train users to avoid clicking untrusted links.

Recommended fix High confidence

10.0.17

  1. 1. Backup the current GLPI database and files before proceeding with the upgrade.
  2. 2. Download GLPI version 10.0.17 from the official GLPI repository or website (github.com/glpi-project/glpi).
  3. 3. Replace the existing GLPI files with the new version 10.0.17 files on the web server.
  4. 4. Navigate to the GLPI web interface to complete the upgrade process, or run the command-line upgrade if applicable.
  5. 5. Verify the installation by logging in and checking that the version shows 10.0.17.
  6. 6. Test that the XSS vulnerability is no longer present by validating the fix.
Caveat Review the GLPI release notes for 10.0.17 to check for any breaking changes or required migration steps before upgrading.

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

Fix this in Glpi Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43418 — 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-43418 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