CVE-2025-21619

CVE-2025-21619 is a critical-severity vulnerability in Glpi-project Glpi with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-89.

Key facts

Description

GLPI is a free asset and IT management software package. An administrator user can perfom a SQL injection through the rules configuration forms. This vulnerability is fixed in 10.0.18.

Frequently asked questions

What is CVE-2025-21619?
GLPI is a free asset and IT management software package. An administrator user can perfom a SQL injection through the rules configuration forms. This vulnerability is fixed in 10.0.18.
How severe is CVE-2025-21619?
CVE-2025-21619 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2025-21619 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (33rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2025-21619?
CVE-2025-21619 affects Glpi-project Glpi. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2025-21619?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
Does CVE-2025-21619 have an EU (EUVD) identifier?
Yes. CVE-2025-21619 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-6703.
When was CVE-2025-21619 published?
CVE-2025-21619 was published on 2025-03-18 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Glpi-project Glpi

All CVEs affecting Glpi-project Glpi →

Other CWE-89 (SQL Injection) vulnerabilities

Browse all CWE-89 (SQL Injection) vulnerabilities →