CVE-2024-41679
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 authenticated user can exploit a SQL injection vulnerability from the ticket form. 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 confidenceGLPI version 10.0.17 addresses a SQL injection vulnerability in the ticket form that can be exploited by an authenticated user to inject malicious SQL queries, potentially allowing unauthorized database access, data exfiltration, or manipulation.
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>= 10.0.0, < 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 versionLocate and read the version file in your GLPI installation directory (commonly version.php or similar), or log into GLPI as an administrator and navigate to Setup > General > System Information to view the installed versionAffected if The installed version is 10.0.0 through 10.0.16 (any version >= 10.0.0 but < 10.0.17)
-
Confirm ticket form module is activeLog into GLPI as an authenticated user and verify that the ticket creation form (usually accessed via the Helpdesk or Assistance menu) is accessible and functionalAffected if The ticket form is accessible to authenticated users in your environment
-
Verify user authentication is enabledCheck that GLPI user authentication is configured and active - confirm that regular user accounts can log in and access the ticket creation featureAffected if Authenticated users can log in and access the ticket form in your GLPI instance
You are affected if your GLPI version is 10.0.0 through 10.0.16 and authenticated users have access to the ticket creation form.
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 remediate the SQL injection vulnerability in the ticket form; ensure proper backup and testing procedures are followed before applying the upgrade.
10.0.17
- 1. Back up the current GLPI installation and database before proceeding with the upgrade.
- 2. Download GLPI version 10.0.17 from the official GitHub repository or the GLPI website.
- 3. Replace the existing GLPI files with the new version 10.0.17 files, preserving the config directory (config/glpi) and any custom plugins.
- 4. Run the GLPI update process by accessing the application in a web browser and following the upgrade wizard.
- 5. Verify the upgrade was successful by logging in and checking the version number.
- 6. Test that ticket creation and related functionality work correctly after the upgrade.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-41679 — 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-41679 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