# GHSA-99r5-84gr-59f6: Leantime has Host Header Injection Vulnerability

> Attackers can manipulate host headers to view unauthorized user details in Leantime, exposing sensitive personal information.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 21 Feb 2025

## What is GHSA-99r5-84gr-59f6?

GHSA-99r5-84gr-59f6 is a vulnerability in leantime/leantime, published on 21 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

### Summary
A host header injection vulnerability has been identified in the user details viewing functionality of the system. This vulnerability allows an attacker to manipulate the host header in HTTP requests, thereby gaining unauthorized access to view details of other users.

## Which versions are affected by GHSA-99r5-84gr-59f6?

2 open source packages ship an affected version, including leantime/leantime.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `leantime/leantime` | Packagist | All versions | 3.1.2 |
| `leantime/leantime` | Packagist | All versions | 3.1.2 |

## How do I fix GHSA-99r5-84gr-59f6?

Upgrade leantime/leantime to 3.1.2 or later.

## Is GHSA-99r5-84gr-59f6 being exploited?

There is no known exploitation of GHSA-99r5-84gr-59f6 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-99r5-84gr-59f6 and fix it if it is affected.

What it is: GHSA-99r5-84gr-59f6 is a vulnerability in leantime/leantime, published on 21 Feb 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of GHSA-99r5-84gr-59f6 in the wild and no public exploit code.

Affected packages and fixed versions:
- leantime/leantime (Packagist): affected all versions; fixed in 3.1.2
- leantime/leantime (Packagist): affected all versions; fixed in 3.1.2

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/GHSA-99r5-84gr-59f6/ (Markdown: https://insights.sbomify.com/GHSA-99r5-84gr-59f6/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-99r5-84gr-59f6

---
From sbomify Insights: https://insights.sbomify.com/GHSA-99r5-84gr-59f6/
Summaries are generated and may contain mistakes; the official description above is the record.