# CVE-2023-46694: File upload in n/a

> Authenticated attackers can upload arbitrary files via the Ckeditor file manager to execute remote commands in Vtenext.

- **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 28 May 2024
- **Updated:** 13 Feb 2025

## What is CVE-2023-46694?

CVE-2023-46694 is a high-severity vulnerability in n/a, published on 28 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Vtenext 21.02 allows an authenticated attacker to upload arbitrary files, potentially enabling them to execute remote commands. This flaw exists due to the application's failure to enforce proper authentication controls when accessing the Ckeditor file manager functionality.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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


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

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

## Is CVE-2023-46694 being exploited?

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

Public exploit code:

- CVE-2023-46694 proof-of-concept (github_poc): https://github.com/invisiblebyte/CVE-2023-46694

## Fix prompt for AI coding agents

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

What it is: CVE-2023-46694 is a high-severity vulnerability in n/a, published on 28 May 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2023-46694 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-46694/ (Markdown: https://insights.sbomify.com/CVE-2023-46694/index.md)
```

## Sources

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

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