# CVE-2022-36112: Blind Server-Side Request Forgery (SSRF) in GLPI

> Attackers can exploit RSS feeds or external calendars to perform blind SSRF, scanning internal ports and services on the GLPI server or private network.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 14 Sep 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-rqgx-gqhp-x8vv, UBUNTU-CVE-2022-36112

## What is CVE-2022-36112?

CVE-2022-36112 is a low-severity server-side request forgery vulnerability in Glpi-Project Glpi, published on 14 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

GLPI stands for Gestionnaire Libre de Parc Informatique and is a Free Asset and IT Management Software package, that provides ITIL Service Desk features, licenses tracking and software auditing. Usage of RSS feeds or extenal calendar in planning is subject to SSRF exploit. Server-side requests can be used to scan server port or services opened on GLPI server or its private network. Queries responses are not exposed to end-user (blind SSRF). Users are advised to upgrade to version 10.0.3 to resolve this issue. There are no known workarounds.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2022-36112?

It affects 1 product.


Products: Glpi-Project Glpi.

## How do I fix CVE-2022-36112?

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

## Is CVE-2022-36112 being exploited?

There is no known exploitation of CVE-2022-36112 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-2022-36112 and fix it if it is affected.

What it is: CVE-2022-36112 is a low-severity server-side request forgery vulnerability in Glpi-Project Glpi, published on 14 Sep 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-36112 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-2022-36112/ (Markdown: https://insights.sbomify.com/CVE-2022-36112/index.md)
```

## Sources

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

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