# CVE-2023-22855: Code injection in n/a

> Remote attackers can execute arbitrary code by exploiting a path traversal vulnerability that allows loading malicious .t4 template files via the web interface.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2023
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-f9jv-w5v2-f33c

## What is CVE-2023-22855?

CVE-2023-22855 is a critical code injection vulnerability in n/a, published on 15 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Kardex Mlog MCC 5.7.12+0-a203c2a213-master allows remote code execution. It spawns a web interface listening on port 8088. A user-controllable path is handed to a path-concatenation method (Path.Combine from .NET) without proper sanitisation. This yields the possibility of including local files, as well as remote files on SMB shares. If one provides a file with the extension .t4, it is rendered with the .NET templating engine mono/t4, which can execute code.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Kardex Kardex Control Center.

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

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

## Is CVE-2023-22855 being exploited?

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

Public exploit code:

- Kardex Mlog MCC 5.7.12 - RCE (Remote Code Execution) (exploitdb)
- Security Vulnerability - Kardex Mlog MCC (github_poc): https://github.com/vianic/CVE-2023-22855

## Fix prompt for AI coding agents

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

What it is: CVE-2023-22855 is a critical code injection vulnerability in n/a, published on 15 Feb 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-22855 exists.

Affected product: n/a. 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-2023-22855/ (Markdown: https://insights.sbomify.com/CVE-2023-22855/index.md)
```

## Sources

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

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