CVE-2025-21619
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 administrator user can perfom a SQL injection through the rules configuration forms. This vulnerability is fixed in 10.0.18.
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.18 contain a SQL injection vulnerability in the rules configuration module. An authenticated administrator user can inject malicious SQL commands through form inputs in the rules configuration area, potentially allowing unauthorized data access, modification, or database compromise.
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.78, < 10.0.18CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify GLPI installation and versionLocate the GLPI installation directory and check the version.php or version.json file, or access the GLPI login page footer which typically displays the version numberAffected if The installed version is 0.78 or higher but lower than 10.0.18
-
Confirm rules configuration module is activeLog into GLPI as an administrator and navigate to the Rules configuration section (typically under Setup > Rules), or check the file system for the rules engine module presenceAffected if The rules configuration module is accessible and active in the GLPI instance
-
Verify administrator-level access existsCheck user accounts with administrator privileges in GLPI by examining the user administration panel or the glpi_users database table for profiles with 'admin' or 'super-admin' rightsAffected if Any authenticated administrator or super-admin user account exists in the system
-
Review database query logs for suspicious activityExamine database logs (MySQL/MariaDB general query log, slow query log, or PostgreSQL logs) for unusual or malformed SQL queries targeting rules-related tables around the time of the rules configuration feature usageAffected if Unexpected or injected SQL patterns appear in database query logs related to the rules configuration functionality
The environment is affected if GLPI version is 0.78 or higher but lower than 10.0.18, the rules configuration module is accessible, and an authenticated administrator account exists that could trigger the SQL injection.
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.18
Upgrade GLPI to version 10.0.18 or later. If immediate upgrade is not possible, restrict administrative access and monitor database query logs for suspicious activity in the rules configuration section.
10.0.18
- Upgrade GLPI to version 10.0.18 to resolve the SQL injection vulnerability in the rules configuration forms
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-21619 — 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-2025-21619 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