How severe is CVE-2017-18362?

CVE-2017-18362 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2017-18362?

Affected package information for CVE-2017-18362 is not yet fully mapped. Check the official advisory links for details.

How do I fix CVE-2017-18362?

No fixed version has been published for CVE-2017-18362 yet. Monitor the advisory for updates, apply mitigations recommended by the vendor, and use O3 Security to track when a fix becomes available in your stack.

Is CVE-2017-18362 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2017-18362, including 3 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2017-18362?

CVE-2017-18362 has an EPSS (Exploit Prediction Scoring System) score of 81.1%, placing it in the 99th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2017-18362 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2017-18362 (Kaseya VSA SQL Injection Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-05-24. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-06-14. The required action was: The impacted product is end-of-life and should be disconnected if still in use. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2017-18362?

CVE-2017-18362 is classified as SQL Injection (CWE-89). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Which products and versions are affected by CVE-2017-18362?

CVE-2017-18362 affects connectwise manageditsync. Check the affected-products list on this page against your deployed version to confirm exposure.

Is there exploit tooling available for CVE-2017-18362?

A Nuclei detection template exists for CVE-2017-18362, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2017-18362 published, and has it been updated?

CVE-2017-18362 was published on February 5, 2019 and was last updated on November 5, 2025. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-05-24 — agencies required to remediate by 2022-06-14 · Ransomware

CVE-2017-18362

CRITICAL

ConnectWise ManagedITSync integration through 2017 for Kaseya VSA is vulnerable to unauthenticated remote commands that allow full direct access to the Kaseya VSA database. In February…

Published

Feb 5, 2019

Updated

Nov 5, 2025

Affected

0 pkgs

Patched

None yet

Exploits

3 known

EPSS Exploitation Probability

via FIRST.org ↗

81.1%probability of exploitation in next 30 days

Very High Risk99th percentile+0.83%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Description

ConnectWise ManagedITSync integration through 2017 for Kaseya VSA is vulnerable to unauthenticated remote commands that allow full direct access to the Kaseya VSA database. In February 2019, attackers have actively exploited this in the wild to download and execute ransomware payloads on all endpoints managed by the VSA server. If the ManagedIT.asmx page is available via the Kaseya VSA web interface, anyone with access to the page is able to run arbitrary SQL queries, both read and write, without authentication.

Affected Products

1 product · 1 configurations

Application

manageditsyncconnectwise

≤ 2017

range

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

ConnectWise ManagedITSync integration through 2017 for Kaseya VSA is vul…

github.comNVDFeb 2019

ConnectWise ManagedITSync integration through 2017 for Kaseya VSA is vul…

nvd.nist.govNVDFeb 2019

ConnectWise ManagedITSync integration through 2017 for Kaseya VSA is vul…

cisa.govCISAMay 2022

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2017-18362 in your stack?

O3 detects CVE-2017-18362 across dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my stack How O3 SCA works