NVD / CVE Program· CNA GitHub_M

CVE-2026-22044: GLPI is Vulnerable to Authenticated SQL Injection

Noroxi assessment

Priority: Monitor (action score 35/100)

The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
Probability of exploitation in the next 30 days: 0.30% (FIRST EPSS).
Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. No user action is required. No special conditions are required; it is repeatable.
Fixed version: glpi-project glpi 10.0.23.
Severity is disputed: the assigning authority (CNA) scores it 6.5, NVD 8.8.

Low priority for now. Upgrade to glpi-project glpi 10.0.23 or later.

Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it

Primary sources: NVD · CVE.org · FIRST EPSS

GLPI is a free asset and IT management software package. From version 0.85 to before 10.0.23, an authenticated user can perform a SQL injection. This issue has been patched in version 10.0.23.

HighCVSS 8.8 · v3.1—No exploit Fix available

SQL injection

BDU:2026-05697

Published: Feb 4, 2026
Updated: Jun 17, 2026
EPSS: 0.3% · 23th percentile
CWE: CWE-89

Report tools

JSON

Action score

Monitor

Low priority for now.

CVSS: 35 / 40 · 8.8 / 10
CISA KEV: 0 / 30 · Not listed
EPSS: 0 / 30 · 0.3%

CISA SSVC decision

Exploitation: none
Automatable: no
Technical impact: partial

Vulnrichment: CISA's decision-tree inputs.

CNA vs NVD score

NVD: 8.8
CNA · GitHub_M: 6.5; 2.3 point gap

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.

Get told when this record changes

Not in KEV: no record of exploitation in the wild
No public exploit code on record
A fix has been released

If any of these changes, we'll tell you in the daily email digest.

Running WordPress? Scan your site free with WP Lens

Is your version affected? Check it

Noroxi analysis

What does it mean in your environment?

The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.

We use this product, ask for help

Affected systems

Is your version affected?

Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.

Vendor	Product	CPE
glpi-project	glpi	cpe:2.3:a:glpi-project:glpi

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

glpi-project glpi0.85 and later · before 10.0.23

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

glpi-project glpi
- >= 0.85, < 10.0.23affected

Same product

glpi-project: all records

Other highest-scoring records for the same primary product.

CVE-2022-35914/vendor/htmlawed/htmlawed/htmLawedTest.php in the htmlawed module for GLPI through 10.0.2 allows PHP code injection.KEV
99Now
CVE-2025-24799GLPI allows unauthenticated SQL injection through the inventory endpoint
65This week
CVE-2023-46727GLPI SQL injection through inventory agent request
59Plan

Published before and after this one in the same product

← EarlierCVE-2025-64516Jan 15, 2026 · GLPI incorrectly authorizes access to documents
30Monitor
← EarlierCVE-2025-66417Jan 15, 2026 · GLPI has an unauthenticated SQL injection through the inventory endpoint
39Monitor
Later →CVE-2026-22247Feb 4, 2026 · GLPI is Vulnerable to SSRF via Webhooks
36Monitor

Remediation

Which version to upgrade to

Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.

Product / package	Fixed version	Source
glpi-project glpi	10.0.23 · description	Vendor (CNA)

Exploit status

No known public exploit

No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.

Research context

For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.

Timeline

From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.

No dated events beyond publication.

No history yet (it accumulates with the daily EPSS job).

Patch and commit links

Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.

No commit or PR link among the references.

Credits

All researchers

Finders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.

No credits in the CNA record.

Variant candidates

Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.

CVE-2025-24799323 days apartGLPI allows unauthenticated SQL injection through the inventory endpoint
65This week
CVE-2024-40638446 days apartGLPI allows account takeover via SQL Injection in AJAX scripts
46Plan
CVE-2026-2626361 days apartGLPI has an Unauthenticated SQL Injection via Search engine
41Plan
CVE-2025-6641720 days apartGLPI has an unauthenticated SQL injection through the inventory endpoint
39Monitor
CVE-2026-2904761 days apartGLPI has an Authenticated SQL Injection via log exports
35Monitor
CVE-2024-45608446 days apartGLPI has an Authenticated SQL Injection
35Monitor

Chain candidates

An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.

—

Bug bounty scope

No known public program.

Source: bounty-targets-data (public HackerOne, Bugcrowd, Intigriti, YesWeHack listings).

Technical details

Attack conditions

Anyone who can reach it over the internet can trigger it.
A low-privileged account is enough.
No user action is required.
No special conditions are required; it is repeatable.

If successful

Confidentiality: high · data can be read
Integrity: high · data or configuration can be modified
Availability: high · the service can be disrupted

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality impact: High
Integrity impact: High
Availability impact: High

Weakness class (CWE)

CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

nvd-primary

Root cause

The query text is built by concatenating user input. The database cannot tell where the data ends and the command begins.

The bug in code

The whole CWE-89 class

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

Vulnerable

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = '" + owner + "'"
4);

Fixed

1const owner = req.query.owner;
2const rows = await db.query(
3  "SELECT * FROM files WHERE owner = $1",
4  [owner]
5);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.

Attack patterns (CAPEC)

ATT&CK techniques

—

Change log

Fix✗ → ✓Sep 29, 2026, 11:55 AM UTC

For records you follow, these changes also arrive as notifications. →

References

github.com/glpi-project/glpi/releases/tag/10.0.23

Show all references (1 more)

github.com/glpi-project/glpi/security/advisories/GHSA-569q-j526-w385

Vendor advisories and official records. Exploit/PoC links are deliberately left out.

All records