Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%
Buy Us a Coffee

CVE-2026-53629— GLPI: SQL injection in history tab

Quick assessment

Affected
glpi-project glpi
Exploitation
Public or AI PoC available; prioritize validation
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

GLPI 是一款免费的资产与 IT 管理软件包。在版本 9.4.0 至 10.0.26 以及 11.0.8 之前的版本中，拥有日志读取权限的攻击者可以构造一个指向“历史记录”（history）选项卡的 URL，从而将攻击者控制的值注入到数据库查询中。这导致通过“历史记录”选项卡的接口可发生 SQL 注入漏洞。该问题已在版本 10.0.26 和 11.0.8 中得到修复。

CVSS 7.1 · High EPSS 1.02% · P62

Public Exploits 1

Nuclei · 1 CVE-2026-53629.yaml [template]
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-53629

Vulnerability Information
Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
GLPI: SQL injection in history tab
Source: CVE Program / CVE List V5
Vulnerability Description
GLPI is a free asset and IT management software package. From 9.4.0 until 10.0.26 and 11.0.8, an attacker with the READ right on logs can craft a URL for the history tab that injects attacker-controlled values into a database query. This permits SQL injection through the history tab endpoint. This issue is fixed in versions 11.0.8 and 10.0.26.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N
Source: CVE Program / CVE List V5
Vulnerability Type
SQL命令中使用的特殊元素转义处理不恰当(SQL注入)
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
glpi-project glpi >= 9.4.0, < 10.0.26 -

II. Public POCs for CVE-2026-53629

# POC Description Source Link Shenlong Link
1 GLPI versions before 10.0.26 and 11.0.8 are vulnerable to a blind SQL injection in the history log filter. The Log::convertFiltersValuesToSqlCriteria() function splits the affected_fields filter into key:operator:value parts and DBmysqlIterator::analyseCrit() does not quote OR, AND and NOT as column names, allowing an authenticated user with logs READ right to inject arbitrary SQL. Verified against glpi/glpi:10.0.25 (Docker + MariaDB): filter "OR::1 AND sleep(5)" produces "... AND (((((1 AND sleep(5))))))" in the query and the request takes ~5s. On 10.0.26 the same payload is rejected (~30ms). https://github.com/projectdiscovery/nuclei-templates/blob/main/http/cves/2026/CVE-2026-53629.yaml POC Details
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-53629

请登录查看更多情报信息。

Other References for CVE-2026-53629 (5)

Same Patch Batch · glpi-project · 2026-09-25 · 13 CVEs total

CVE-2026-48482 9.4 CRITICAL GLPI: RCE via Form import
CVE-2026-47679 8.5 HIGH GLPI: arbitrary file deletion
CVE-2026-55214 8.5 HIGH GLPI: Stored XSS in suppliers
CVE-2026-49470 7.7 HIGH GLPI: Missing Rate Limiting on Login and TOTP Verification — Account Takeover via Brute Fo
CVE-2026-53625 7.5 HIGH GLPI: Privilege Escalation via authtype API manipulation
CVE-2026-53610 7.5 HIGH GLPI: Reflected XSS in dashboards
CVE-2026-53626 7.1 HIGH GLPI: Arbitrary Document Read via Form Context Authorization Bypass
CVE-2026-53627 6.0 MEDIUM GLPI: Unexpected access to update operations through the API
CVE-2026-53628 5.9 MEDIUM GLPI: Unallowed authentication method update by administrator
CVE-2026-45801 5.3 MEDIUM GLPI: Unauthorized Debug Mode Activation via Profile Update (Privilege Escalation)
CVE-2026-55217 5.3 MEDIUM GLPI: Unallowed modfication of knowbase items comments and translations
CVE-2026-49469 4.6 MEDIUM GLPI: LDAP filter injection in user import feature

IV. Related Vulnerabilities

Same product: glpi
Same vendor: glpi-project
Same weakness: CWE-89

V. Comments for CVE-2026-53629

No comments yet

Leave a comment