# CVE-2019-11445: File upload in n/a

> Attackers can upload malicious JSP files to achieve remote code execution with root privileges on OpenKM document management systems.

- **Severity:** High 7.2 (`CVSS:3.0/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:** No
- **Published:** 22 Apr 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8q66-6rmh-7w5v

## What is CVE-2019-11445?

CVE-2019-11445 is a high-severity vulnerability in n/a, published on 22 Apr 2019. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

OpenKM 6.3.2 through 6.3.7 allows an attacker to upload a malicious JSP file into the /okm:root directories and move that file to the home directory of the site, via frontend/FileUpload and admin/repository_export.jsp. This is achieved by interfering with the Filesystem path control in the admin's Export field. As a result, attackers can gain remote code execution through the application server with root privileges.

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

## Which versions are affected by CVE-2019-11445?

It affects 1 product.


Products: Openkm Openkm.

## How do I fix CVE-2019-11445?

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

## Is CVE-2019-11445 being exploited?

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

Public exploit code:

- OpenKM 6.3.2 < 6.3.7 - Remote Command Execution (Metasploit) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2022-2131](https://insights.sbomify.com/CVE-2022-2131/): OpenKM XXE Injection (high 8.5)
- [CVE-2021-33950](https://insights.sbomify.com/CVE-2021-33950/): XML external entity in n/a (high 7.5)
- [CVE-2012-2316](https://insights.sbomify.com/CVE-2012-2316/): Cross-site request forgery in n/a (medium 6.8)
- [CVE-2024-35475](https://insights.sbomify.com/CVE-2024-35475/): Cross-site request forgery in n/a (medium 6.4)
- [CVE-2025-57244](https://insights.sbomify.com/CVE-2025-57244/): Cross-site scripting in n/a (medium 5.4)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-11445 and fix it if it is affected.

What it is: CVE-2019-11445 is a high-severity vulnerability in n/a, published on 22 Apr 2019. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-11445 in the wild and no public exploit code.

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

## Sources

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

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