# GHSA-v4q9-437p-mhpg: Leantime allows Cross Site Scripting (XSS) and SQL Injection (SQLi)

> Attackers can inject malicious scripts via unsanitized GET parameters in Leantime, leading to code execution or data theft.

- **Severity:** Not scored
- **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:** Yes
- **Published:** 21 Feb 2025

## What is GHSA-v4q9-437p-mhpg?

GHSA-v4q9-437p-mhpg is a cross-site scripting vulnerability in leantime/leantime, published on 21 Feb 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

### Summary
A cross-site scripting (XSS) vulnerability has been identified in Leantime. The vulnerability allows an attacker to inject malicious scripts into certain fields, potentially leading to the execution of arbitrary code or unauthorized access to user-sensitive information. The code does not include any validation or sanitization of the $_GET["id"] parameter. As a result, it directly incorporates the user-supplied value into the source path without any checks.

## Which versions are affected by GHSA-v4q9-437p-mhpg?

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-v4q9-437p-mhpg?

Upgrade leantime/leantime to 3.3 or later.

## Is GHSA-v4q9-437p-mhpg being exploited?

There is no known exploitation of GHSA-v4q9-437p-mhpg in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-v4q9-437p-mhpg and fix it if it is affected.

What it is: GHSA-v4q9-437p-mhpg is a cross-site scripting vulnerability in leantime/leantime, published on 21 Feb 2025. 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 GHSA-v4q9-437p-mhpg 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-v4q9-437p-mhpg/ (Markdown: https://insights.sbomify.com/GHSA-v4q9-437p-mhpg/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-v4q9-437p-mhpg

---
From sbomify Insights: https://insights.sbomify.com/GHSA-v4q9-437p-mhpg/
Summaries are generated and may contain mistakes; the official description above is the record.