# CVE-2024-51747: Arbitrary File Read and Delete in kanboard

> Authenticated admins can read and delete arbitrary server files by uploading a modified SQLite database with path traversal payloads.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 11 Nov 2024
- **Updated:** 12 Nov 2024
- **Also known as:** GHSA-78pf-vg56-5p8v

## What is CVE-2024-51747?

CVE-2024-51747 is a critical path traversal vulnerability in kanboard, published on 11 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Kanboard is project management software that focuses on the Kanban methodology. An authenticated Kanboard admin can read and delete arbitrary files from the server. File attachments, that are viewable or downloadable in Kanboard are resolved through its `path` entry in the `project_has_files`  SQLite db. Thus, an attacker who can upload a modified sqlite.db through the dedicated feature, can set arbitrary file links, by abusing path traversals. Once the modified db is uploaded and the project page is accessed, a file download can be triggered and all files, readable in the context of the Kanboard application permissions, can be downloaded. This issue has been addressed in version 1.2.42 and all users are advised to upgrade. There are no known workarounds for this vulnerability.

Weakness: CWE-27 (Path Traversal: 'dir/../../filename'), CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Kanboard Kanboard.

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

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

## Is CVE-2024-51747 being exploited?

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

Public exploit code:

- https://github.com/l20170217b/CVE-2024-51747 (github_poc): https://github.com/l20170217b/CVE-2024-51747

## 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-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)
- [CVE-2017-12851](https://insights.sbomify.com/CVE-2017-12851/): Business logic in n/a (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51747 is a critical path traversal vulnerability in kanboard, published on 11 Nov 2024. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-51747 exists.

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

## Sources

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

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