CVE-2017-18362: Kaseya VSA SQL Injection Vulnerability
Affects Kaseya Virtual System/Server Administrator (VSA)Source CISA KEV
Exploited in the wild · used in ransomware campaigns · KEV due 14 Jun 2022 · public detection template (Nuclei) · 86% EPSS : apply the vendor's fix or mitigations to Kaseya Virtual System/Server Administrator (VSA) now.
Data as of 10/24/2026, 22:15:59 UTC
- Exploitation
Actively exploited – in CISA KEV since 05/24/2022
- KEV deadline
- 06/14/2022 US federal agencies must patch by this date; a sensible deadline for everyone else.
- Ransomware
- Used in ransomware campaigns
- EPSS
- 86.8% chance of exploitation in 30 days – higher than 99% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Public exploits
- a Nuclei detection templatePublic attack or detection tooling exists; see Public exploits below.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HWhat to do
CISA required action
The impacted product is end-of-life and should be disconnected if still in use.
Public exploits and detection
Nuclei detection templates
Public tooling indexed from Metasploit Framework, Exploit-DB and ProjectDiscovery nuclei-templates. Its existence raises the odds of exploitation; it does not confirm attacks.
Description
ConnectWise ManagedITSync integration for Kaseya VSA is vulnerable to unauthenticated remote commands that allow full direct access to the Kaseya VSA database.
Weaknesses
- CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.