# CVE-2024-45611: GLPI has a stored XSS at src/RSSFeed.php

> An authenticated user can inject malicious scripts into RSS feeds, leading to stored XSS and potential account takeover in GLPI.

- **Severity:** Medium 5.7 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 Nov 2024
- **Updated:** 19 Nov 2024
- **Also known as:** GHSA-j73h-x6j3-m479, UBUNTU-CVE-2024-45611

## What is CVE-2024-45611?

CVE-2024-45611 is a medium-severity cross-site scripting vulnerability in Glpi-Project Glpi, published on 15 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

GLPI is an open-source asset and IT management software package that provides ITIL Service Desk features, licenses tracking and software auditing. An authenticated user can bypass the access control policy to create a private RSS feed attached to another user account and use a malicious payload to triggger a stored XSS. Upgrade to 10.0.17.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-45611?

It affects 1 product.


Products: Glpi-Project Glpi.

## How do I fix CVE-2024-45611?

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

## Is CVE-2024-45611 being exploited?

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

What it is: CVE-2024-45611 is a medium-severity cross-site scripting vulnerability in Glpi-Project Glpi, published on 15 Nov 2024. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-45611 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-2024-45611/ (Markdown: https://insights.sbomify.com/CVE-2024-45611/index.md)
```

## Sources

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

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