# GHSA-92xh-6x7v-4rmq: Leantime allows Cross-Site Request Forgery (CSRF)

> A CSRF vulnerability allows attackers to create high-privilege accounts by tricking administrators into clicking a malicious link.

- **Severity:** Not scored
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **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-92xh-6x7v-4rmq?

GHSA-92xh-6x7v-4rmq is a vulnerability in leantime/leantime, published on 21 Feb 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

**CSRF**
### Summary
A cross-site request forgery vulnerability allows a remote actor to create an account with Owner privileges. By luring an Owner or Administrator into clicking a button on an attacker-controlled website, a request will be issued, generating an account with the attacker's information and role of their choosing. 

### Impact
While the likelihood of a successful exploit is low, the impact would be high as the attacker could then gain complete control over the victim's environment.

## Which versions are affected by GHSA-92xh-6x7v-4rmq?

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-92xh-6x7v-4rmq?

Upgrade leantime/leantime to 3.1.2 or later.

## Is GHSA-92xh-6x7v-4rmq being exploited?

There is no known exploitation of GHSA-92xh-6x7v-4rmq in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for GHSA-92xh-6x7v-4rmq and fix it if it is affected.

What it is: GHSA-92xh-6x7v-4rmq is a vulnerability in leantime/leantime, published on 21 Feb 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of GHSA-92xh-6x7v-4rmq 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-92xh-6x7v-4rmq/ (Markdown: https://insights.sbomify.com/GHSA-92xh-6x7v-4rmq/index.md)
```

## Sources

- OSV: https://osv.dev/vulnerability/GHSA-92xh-6x7v-4rmq

---
From sbomify Insights: https://insights.sbomify.com/GHSA-92xh-6x7v-4rmq/
Summaries are generated and may contain mistakes; the official description above is the record.