# CVE-2024-51748: Remote code execution through language setting in kanboard

> An authenticated admin can achieve remote code execution by uploading a crafted database that uses path traversal to load malicious PHP files.

- **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-jvff-x577-j95p

## What is CVE-2024-51748?

CVE-2024-51748 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 run arbitrary php code on the server in combination with a file write possibility. The user interface language is determined and loaded by the setting `application_language` in the `settings` table. Thus, an attacker who can upload a modified sqlite.db through the dedicated feature, has control over the filepath, which is loaded. Exploiting this vulnerability has one constraint: the attacker must be able to place a file (called translations.php) on the system. However, this is not impossible, think of anonymous FTP server or another application that allows uploading files. Once the attacker has placed its file with the actual php code as the payload, the attacker can craft a sqlite db settings, which uses path traversal to point to the directory, where the `translations.php` file is stored. Then gaining code execution after importing the crafted sqlite.db. 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-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Kanboard Kanboard.

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

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

## Is CVE-2024-51748 being exploited?

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

## 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-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-51748 and fix it if it is affected.

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

## Sources

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

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