Skip to main content
VulnerabilityPublished

CVE-2026-48728: glpi-inventory-plugin · Missing Authentication for Critical Functionality

Affects glpi-inventory-pluginSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.9 Medium : upgrade to 1.6.8 when convenient.

Data as of 18 Nov 2026, 16:07 UTC

CVSS 4.0 base score
6.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (GitHub_M)CVSS 4.06.9
Patch
Available – fixed in 1.6.8
CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:L/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade glpi-inventory-plugin to 1.6.8.

Affected software

ProductAffectedFixed in
glpi-projectglpi-inventory-pluginAffected
  • <1.6.8
Fixed in
  • 1.6.8

AI-suggested

Upgrade the GLPI Inventory Plugin to version 1.6.8 or later, where the authentication issue has been fixed. No other mitigation is required as the vendor has provided an official fix.

Description

CVE-2026-48728 is a vulnerability in the GLPI Inventory Plugin versions prior to 1.6.8 where critical agent API endpoints lack authentication. Specifically, the /b/deploy, /b/collect, and /b/esx endpoints do not verify requests before processing Deploy, Collect, and ESX tasks. This allows unauthenticated remote attackers to enumerate jobs and manipulate their status, potentially disclosing sensitive job information and interfering with task processing. The issue is resolved in version 1.6.8.

References

Community reviews

Loading reviews…