dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2025-32786

HIGH · 7.5 CVSS v3.1 Published 2025-11-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
The GLPI Inventory Plugin handles network discovery, inventory, software deployment, and data collection for GLPI agents. Versions 1.5.0 and below are vulnerable to SQL Injection. This issue is fixed in version 1.5.1.

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

SQL Injection vulnerability in GLPI Inventory Plugin versions 1.5.0 and below. The plugin is used for network discovery, inventory, software deployment, and data collection for GLPI agents. Attackers can inject malicious SQL queries through unsanitized input in plugin functions.

MitigationUpgrade GLPI Inventory Plugin to version 1.5.1 to remediate the SQL Injection vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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. Verify GLPI Inventory Plugin is installed
    Check the GLPI plugin directory or access the Plugins section in the GLPI administration interface to confirm the GLPI Inventory Plugin is present
    Affected if plugin is installed and listed in GLPI plugin management
  2. Determine installed plugin version
    Access the Plugins section in GLPI administration panel; the version is typically displayed in the plugin listing, or inspect the plugin's version.php file if you have file system access
    Affected if version is 1.5.0 or lower
  3. Confirm plugin is active
    In GLPI administration, verify the plugin status shows as 'Enabled' or 'Active' rather than 'Disabled' or 'Not active'
    Affected if plugin is enabled and running in the GLPI instance
  4. Check for SQL injection entry points
    Review plugin configuration files and functions that handle user-supplied input, particularly in discovery, inventory, or deployment-related functions mentioned in the vulnerability description
    Affected if plugin processes external input without sanitization in database queries

User is affected if GLPI Inventory Plugin versions 1.5.0 or below is installed and enabled in their GLPI environment.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade GLPI Inventory Plugin to version 1.5.1 to remediate the SQL Injection vulnerability.

Recommended fix High confidence

1.5.1

  1. Identify the GLPI Inventory Plugin currently installed on your system
  2. Backup your current GLPI instance and database before proceeding
  3. Download GLPI Inventory Plugin version 1.5.1 from the official GitHub repository or GLPI marketplace
  4. Upload the new version to your GLPI plugins directory, replacing the existing installation
  5. Clear any caches if applicable and verify the plugin is properly loaded
  6. Test that the SQL injection vulnerability is no longer present by verifying the fix

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

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 locally
dbcve dependency scanner

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