CVE-2019-11445 in the critical feed json
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…
published 2019-04-22 7 y ago modified 2026-06-17 4 mo ago also EUVD-2019-3120
- cvss
- 7.2
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 14.2%
- EPSS 14.2% chance of exploitation in 30 days, percentile 96%
- public exploits
- 1
- Exploit-DB
Summary
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.
Patch / fix
- openkm openkm 6.3.7
Timeline
- First public exploit (EDB-46526)
- Published
Exploit prediction
14.22% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-46526 OpenKM 6.3.2 < 6.3.7 - Remote Command Execution (Metasploit) webapps, 2019-03-11
- pentest.com.tr https://pentest.com.tr/exploits/OpenKM-DM-6-3-7-Remote-Command-Execution-Metasploit.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.2 | CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 9.0 | AV:N/AC:L/Au:S/C:C/I:C/A:C |
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
exploit-db.com
/exploits/46526
exploit, third-party-advisory, vdb-entry
-
pentest.com.tr
/exploits/OpenKM-DM-6-3-7-Remote-Command-Execution-Metasploit.html
exploit, third-party-advisory
Sources
- CVE List CVE-2019-11445
- NVD CVE-2019-11445
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.