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.
Security readout for executives and security teams
Plain-English summary
This flaw lets an unauthenticated internet attacker upload a server-side file through Kaseya KServer and potentially run code on the server. For organizations still running versions before 6.3.0.2, this is a high-urgency remote compromise risk. The source bundle says Kaseya resolved it by removing the vulnerable endpoint.
Executive priority
Prioritize immediate assessment if Kaseya KServer exists in the environment. Unauthenticated remote code execution against management infrastructure can lead to broad operational impact, and public exploit references increase urgency for legacy deployments.
Technical view
CVE-2013-10034 is a CWE-434 unrestricted file upload in Kaseya KServer before 6.3.0.2. The uploadImage.asp endpoint allowed crafted multipart uploads with path-controlling filenames, enabling ASP content placement in web-accessible locations and code execution as IUSR. CVSS is 9.3 critical under CVSS 4.0.
Likely exposure
Exposure is most likely where legacy Kaseya KServer instances before 6.3.0.2 remain reachable, especially from the internet. Evidence in the bundle does not identify current exposed populations or supported product status beyond the described vulnerable versions.
Exploitation context
The bundle cites public exploit references and technical advisories, including Metasploit and Exploit-DB entries. It does not state CISA KEV inclusion or confirmed active exploitation. Treat exploitability as practical, but do not claim active exploitation from these sources alone.
Researcher notes
The affected statement in the bundle is clearer in prose than in the structured affected array. Base scope on Kaseya KServer before 6.3.0.2 unless additional vendor data narrows it. Avoid overstating active exploitation because KEV is false and no cited source confirms campaigns.
Mitigation direction
Upgrade Kaseya KServer to version 6.3.0.2 or later.
Confirm the vulnerable uploadImage.asp endpoint has been removed.
Restrict external access to Kaseya management interfaces where possible.
Review current Kaseya vendor guidance for supported remediation details.
Validation and detection
Inventory all Kaseya KServer instances and record exact versions.
Check exposed servers for the presence of uploadImage.asp.
Review web logs for unauthenticated uploadImage.asp access.
Inspect web-accessible directories for unexpected ASP files.
Verify remediation in staging before production rollout where feasible.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · medium confidence lookup
CWE-434: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
5Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: pocAutomatable: yesTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-434 · source CWE mapping
Unrestricted Upload of File with Dangerous Type
Unrestricted Upload of File with Dangerous Type represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.