# CVE-2025-27147: GLPI Inventory plugin has Improper Access Control Vulnerability

> Attackers can exploit improper access control in the GLPI Inventory plugin to read or modify files via path traversal.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Mar 2025
- **Updated:** 25 Mar 2025
- **Also known as:** GHSA-h6x9-jm98-cw7c

## What is CVE-2025-27147?

CVE-2025-27147 is a high-severity path traversal vulnerability in glpi-project glpi-inventory-plugin, published on 25 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

The GLPI Inventory Plugin handles various types of tasks for GLPI agents, including network discovery and inventory (SNMP), software deployment, VMWare ESX host remote inventory, and data collection (files, Windows registry, WMI). Versions prior to 1.5.0 have an improper access control vulnerability. Version 1.5.0 fixes the vulnerability.

Weakness: CWE-552 (Files or Directories Accessible to External Parties), CWE-73 (External Control of File Name or Path), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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


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

No fix has been published for CVE-2025-27147 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-27147 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-27147 is a high-severity path traversal vulnerability in glpi-project glpi-inventory-plugin, published on 25 Mar 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-27147 in the wild and no public exploit code.

Affected product: glpi-project glpi-inventory-plugin. 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-27147/ (Markdown: https://insights.sbomify.com/CVE-2025-27147/index.md)
```

## Sources

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

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