# CVE-2024-36399: Kanboard affected by Project Takeover via IDOR in ProjectPermissionController

> A Project Manager can take over any other project by bypassing authorization checks on the POST body project ID.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A: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:** 6 Jun 2024
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-x8v7-3ghx-65cv

## What is CVE-2024-36399?

CVE-2024-36399 is a high-severity missing authorization vulnerability in kanboard, published on 6 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Kanboard is project management software that focuses on the Kanban methodology. The vuln is in app/Controller/ProjectPermissionController.php function addUser(). The users permission to add users to a project only get checked on the URL parameter project_id. If the user is authorized to add users to this project the request gets processed. The users permission for the POST BODY parameter project_id does not get checked again while processing. An attacker with the 'Project Manager' on a single project may take over any other project. The vulnerability is fixed in 1.2.37.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key), CWE-285 (Improper Authorization), CWE-284 (Improper Access Control)

## Which versions are affected by CVE-2024-36399?

It affects 1 product.


Products: Kanboard Kanboard.

## How do I fix CVE-2024-36399?

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

## Is CVE-2024-36399 being exploited?

There is no known exploitation of CVE-2024-36399 in the wild and no public exploit code.

## Other vulnerabilities in kanboard

- [CVE-2026-21881](https://insights.sbomify.com/CVE-2026-21881/): Kanboard is Vulnerable to Reverse Proxy Authentication Bypass (critical 9.1)
- [CVE-2025-55010](https://insights.sbomify.com/CVE-2025-55010/): Kanboard Authenticated Admin Remote Code Execution via Unsafe Deserialization of Events (critical 9.1)
- [CVE-2024-51747](https://insights.sbomify.com/CVE-2024-51747/): Arbitrary File Read and Delete in kanboard (critical 9.1)
- [CVE-2024-51748](https://insights.sbomify.com/CVE-2024-51748/): Remote code execution through language setting in kanboard (critical 9.1)
- [CVE-2017-12850](https://insights.sbomify.com/CVE-2017-12850/): Business logic in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-36399 and fix it if it is affected.

What it is: CVE-2024-36399 is a high-severity missing authorization vulnerability in kanboard, published on 6 Jun 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2024-36399 in the wild and no public exploit code.

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

## Sources

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

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