dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-11321

MEDIUM · 6.4 CVSS v3.1 Published 2026-07-10
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable 6 weeks old

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 DataInjection plugin for GLPI 2.15.6 (GLPI 11 builds) concatenates user-supplied CSV field values directly into SQL queries during CSV import, without parameterization or escaping, resulting in authenticated SQL injection. An authenticated user with access to the Data injection feature can embed SQL expressions such as SLEEP() in a mapped field (for example Serial Number) to manipulate the generated query and extract database information via time-based blind injection.

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

The DataInjection plugin for GLPI concatenates CSV field values directly into SQL queries during import without parameterization or escaping. An authenticated user with DataInjection access can embed SQL expressions like SLEEP() into mapped fields (e.g., Serial Number), enabling time-based blind SQL injection to extract database information.

MitigationReplace direct string concatenation with parameterized queries/prepared statements for all SQL queries incorporating user-supplied CSV data. Apply input validation as defense-in-depth and restrict DataInjection feature access to minimal required users.

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
High
Privileges
High
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:R/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 checks

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

  1. Confirm GLPI installation exists
    Check for GLPI by looking for its characteristic directories (like 'glpi/', 'front/', 'inc/') or its configuration file (like 'config_db.php') in the web root. Access the GLPI login page via HTTP to verify the application is running.
    Affected if GLPI is not installed - the vulnerability does not apply.
  2. Identify if DataInjection plugin is installed
    Check the GLPI plugins directory (commonly at 'glpi/plugins/' or '/var/www/html/glpi/plugins/') for a DataInjection plugin folder. Alternatively, log into GLPI as an administrator and navigate to Setup > Plugins to list all installed plugins.
    Affected if DataInjection plugin is not installed - the vulnerability does not apply.
  3. Check DataInjection plugin version
    In the GLPI admin interface under Setup > Plugins, locate the DataInjection plugin entry and note its version number. If using the file system, check the plugin's main PHP file (e.g., 'setup.php' or 'plugin.xml') for the version declaration.
    Affected if Plugin version is within the affected range (older, unpatched versions contain the flaw).
  4. Verify DataInjection module is enabled
    Log into GLPI as an administrator, go to Setup > Plugins, and confirm the DataInjection plugin shows as 'Enabled' (not 'Disabled' or 'Not installed'). Alternatively, check the 'glpi_plugin_datainjection_profile' database table or the plugin configuration files.
    Affected if The plugin is disabled - the injection point is not accessible.
  5. Confirm user has DataInjection access rights
    In GLPI, go to Administration > Profiles, select a profile, and check if the 'DataInjection' permission is granted under the Profile tab. Alternatively, query the 'glpi_profiles_users' table joined with 'glpi_plugin_datainjection_profiles' to identify users with DataInjection rights.
    Affected if No user has DataInjection access - the vulnerability cannot be exploited, though the flaw still exists in code.

A user is affected if GLPI with the DataInjection plugin is installed, the plugin is enabled, and at least one authenticated user has DataInjection access rights, allowing them to inject SQL via CSV field mapping.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace direct string concatenation with parameterized queries/prepared statements for all SQL queries incorporating user-supplied CSV data. Apply input validation as defense-in-depth and restrict DataInjection feature access to minimal required users.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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