# CVE-2013-10034: Kaseya < 6.3.0.2 uploadImage.asp Arbitrary File Upload RCE

> Unauthenticated attackers can upload malicious ASP files to execute arbitrary code on Kaseya KServer via the uploadImage.asp endpoint.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Jul 2025
- **Updated:** 15 May 2026
- **Also known as:** GHSA-86jp-9w2g-x862

## What is CVE-2013-10034?

CVE-2013-10034 is a critical vulnerability in Kaseya KServer, published on 31 Jul 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An unrestricted file upload vulnerability exists in Kaseya KServer versions prior to 6.3.0.2. The uploadImage.asp endpoint allows unauthenticated users to upload files to arbitrary paths via a crafted filename parameter in a multipart/form-data POST request. Due to the lack of authentication and input sanitation, an attacker can upload a file with an .asp extension to a web-accessible directory, which can then be invoked to execute arbitrary code with the privileges of the IUSR account. The vulnerability enables remote code execution without prior authentication and was resolved in version 6.3.0.2 by removing the vulnerable uploadImage.asp endpoint.

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

## Which versions are affected by CVE-2013-10034?


## How do I fix CVE-2013-10034?

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

## Is CVE-2013-10034 being exploited?

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

Public exploit code:

- Kaseya uploadImage Arbitrary File Upload (metasploit)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2013-10034 and fix it if it is affected.

What it is: CVE-2013-10034 is a critical vulnerability in Kaseya KServer, published on 31 Jul 2025. 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-2013-10034 exists.

Affected product: Kaseya KServer. 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-2013-10034/ (Markdown: https://insights.sbomify.com/CVE-2013-10034/index.md)
```

## Sources

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

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