# CVE-2023-46245: Kimai (Authenticated) SSTI to RCE by Uploading a Malicious Twig File

> Authenticated attackers can achieve remote code execution by uploading malicious Twig files in Kimai time-tracking application.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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:** Yes
- **Published:** 31 Oct 2023
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-fjhg-96cp-6fcw

## What is CVE-2023-46245?

CVE-2023-46245 is a high-severity code injection vulnerability in kimai, published on 31 Oct 2023. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Kimai is a web-based multi-user time-tracking application. Versions prior to 2.1.0 are vulnerable to a Server-Side Template Injection (SSTI) which can be escalated to Remote Code Execution (RCE). The vulnerability arises when a malicious user uploads a specially crafted Twig file, exploiting the software's PDF and HTML rendering functionalities. Version 2.1.0 enables security measures for custom Twig templates.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

## Which versions are affected by CVE-2023-46245?

2 open source packages ship an affected version, including kimai/kimai. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `kimai/kimai` | Packagist | All versions | 2.1.0 |
| `kimai/kimai` | Packagist | All versions | 2.1.0 |

Products: Kimai Kimai.

## How do I fix CVE-2023-46245?

Upgrade kimai/kimai to 2.1.0 or later.

## Is CVE-2023-46245 being exploited?

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

## Other vulnerabilities in kimai

- [CVE-2020-19825](https://insights.sbomify.com/CVE-2020-19825/): Cross-site Scripting in kimai/kimai (critical 9.6)
- [CVE-2023-53957](https://insights.sbomify.com/CVE-2023-53957/): Kimai 1.30.10 SameSite Cookie Vulnerability Session Hijacking (high 8.5)
- [CVE-2021-43515](https://insights.sbomify.com/CVE-2021-43515/): Improper Neutralization of Formula Elements in a CSV File in Kimai 2 (high 7.8)
- [CVE-2026-23626](https://insights.sbomify.com/CVE-2026-23626/): Kimai Vulnerable to Authenticated Server-Side Template Injection (SSTI) (medium 6.8)
- [CVE-2024-29200](https://insights.sbomify.com/CVE-2024-29200/): API returns timesheet entries a user should not be authorized to view (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-46245 and fix it if it is affected.

What it is: CVE-2023-46245 is a high-severity code injection vulnerability in kimai, published on 31 Oct 2023. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2023-46245 in the wild and no public exploit code.

Affected packages and fixed versions:
- kimai/kimai (Packagist): affected all versions; fixed in 2.1.0
- kimai/kimai (Packagist): affected all versions; fixed in 2.1.0

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

## Sources

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

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