# CVE-2026-92772: Leantime before 3.9.6 Unauthorized Plugin Installation via HTMX

> Authenticated users with limited roles can bypass authorization to install malicious plugins, potentially leading to code execution and privilege escalation.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Sep 2026
- **Updated:** 17 Sep 2026
- **Also known as:** GHSA-7j6f-xmpq-5jjm

## What is CVE-2026-92772?

CVE-2026-92772 is a high-severity missing authorization vulnerability in leantime, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Leantime before 3.9.6 contains an authorization bypass vulnerability in the HTMX plugin install endpoint that lacks permission validation. Authenticated users with limited roles can install marketplace plugins and control arbitrary properties including identifier, version, and license key to deploy malicious plugins.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2026-92772?


## How do I fix CVE-2026-92772?

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

## Is CVE-2026-92772 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92772 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92772 and fix it if it is affected.

What it is: CVE-2026-92772 is a high-severity missing authorization vulnerability in leantime, published on 16 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92772 exists.

Affected product: leantime. 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-2026-92772/ (Markdown: https://insights.sbomify.com/CVE-2026-92772/index.md)
```

## Sources

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

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