# GHSA-3hfj-qcvj-4hx8: Leantime has Missing Authorization Check for Host Parameter

> Authenticated users can view other users' profile information by manipulating the Host parameter due to missing authorization checks.

- **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-3hfj-qcvj-4hx8?

GHSA-3hfj-qcvj-4hx8 is a missing authorization 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

### Finding Description
Application has functionality for a user to view profile information. It does not have an implemented authorization check for "Host" parameter which allows a user to view profile information of another user by replacing "Host" parameter.

### Impact
By exploiting this vulnerability an attacker can able to view profile information (but not anything else or change anything)

## Which versions are affected by GHSA-3hfj-qcvj-4hx8?

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


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

## How do I fix GHSA-3hfj-qcvj-4hx8?

Upgrade leantime/leantime to 3.3 or later.

## Is GHSA-3hfj-qcvj-4hx8 being exploited?

There is no known exploitation of GHSA-3hfj-qcvj-4hx8 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-3hfj-qcvj-4hx8 and fix it if it is affected.

What it is: GHSA-3hfj-qcvj-4hx8 is a missing authorization 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-3hfj-qcvj-4hx8 in the wild and no public exploit code.

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

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-3hfj-qcvj-4hx8/ (Markdown: https://insights.sbomify.com/GHSA-3hfj-qcvj-4hx8/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-3hfj-qcvj-4hx8

---
From sbomify Insights: https://insights.sbomify.com/GHSA-3hfj-qcvj-4hx8/
Summaries are generated and may contain mistakes; the official description above is the record.