# CVE-2025-21626: GLPI vulnerable to exposure of sensitive information in the `status.php` endpoint


- **Severity:** Medium 5.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 25 Feb 2025
- **Updated:** 25 Feb 2025
- **Also known as:** CLEANSTART-2026-AJ93268, GHSA-5vvr-pxwf-3w77, UBUNTU-CVE-2025-21626

## What is CVE-2025-21626?

CVE-2025-21626 is a medium-severity vulnerability in Glpi-Project Glpi, published on 25 Feb 2025. 

### Official description

GLPI is a free asset and IT management software package. Starting in version 0.71 and prior to version 10.0.18, an anonymous user can fetch sensitive information from the `status.php` endpoint. Version 10.0.18 contains a fix for the issue. Some workarounds are available. One may delete the `status.php` file, restrict its access, or remove any sensitive values from the `name` field of the active LDAP directories, mail servers authentication providers and mail receivers.

Weakness: CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

## Which versions are affected by CVE-2025-21626?

It affects 1 product.


Products: Glpi-Project Glpi.

## How do I fix CVE-2025-21626?

Upgrade to a fixed version.

## Is CVE-2025-21626 being exploited?

There is no known exploitation of CVE-2025-21626 in the wild and no public exploit code.

## Other vulnerabilities in Glpi-Project Glpi

- [CVE-2022-35914](https://insights.sbomify.com/CVE-2022-35914/): Teclib GLPI Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2023-42802](https://insights.sbomify.com/CVE-2023-42802/): GLPI vulnerable to unallowed PHP script execution (critical 10.0)
- [CVE-2023-28849](https://insights.sbomify.com/CVE-2023-28849/): GLPI vulnerable to SQL injection and Stored XSS via inventory agent request (critical 10.0)
- [CVE-2022-35947](https://insights.sbomify.com/CVE-2022-35947/): SQL injection in GLPI (critical 10.0)
- [CVE-2022-31056](https://insights.sbomify.com/CVE-2022-31056/): SQL injection with _actor parameter in GLPI (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-21626 and fix it if it is affected.

What it is: CVE-2025-21626 is a medium-severity vulnerability in Glpi-Project Glpi, published on 25 Feb 2025. 
Exploitation: There is no known exploitation of CVE-2025-21626 in the wild and no public exploit code.

Affected product: Glpi-Project Glpi. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-21626/ (Markdown: https://insights.sbomify.com/CVE-2025-21626/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-21626
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-21626
- OSV: https://osv.dev/vulnerability/CVE-2025-21626

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-21626/
Summaries are generated and may contain mistakes; the official description above is the record.