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

> Remote attackers can upload files without extensions, bypassing extension restrictions, potentially leading to code execution.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 26 Sep 2019
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jfrg-795f-64q8

## What is CVE-2019-15862?

CVE-2019-15862 is a high-severity vulnerability in n/a, published on 26 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An issue was discovered in CKFinder through 2.6.2.1. Improper checks of file names allows remote attackers to upload files without any extension (even if the application was configured to accept files only with a defined set of extensions). This affects CKFinder for ASP, CKFinder for ASP.NET, CKFinder for ColdFusion, and CKFinder for PHP.

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

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

It affects 1 product.


Products: Cksource Ckfinder.

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

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

## Is CVE-2019-15862 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63830](https://insights.sbomify.com/CVE-2025-63830/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2019-15891](https://insights.sbomify.com/CVE-2019-15891/): Information disclosure in n/a (medium 5.3)
- [CVE-2016-20023](https://insights.sbomify.com/CVE-2016-20023/): Path traversal in CKFinder (medium 5.0)

## Fix prompt for AI coding agents

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

What it is: CVE-2019-15862 is a high-severity vulnerability in n/a, published on 26 Sep 2019. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2019-15862 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-15862/ (Markdown: https://insights.sbomify.com/CVE-2019-15862/index.md)
```

## Sources

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

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