HIGH · CVSS 8.4 CISA Known Exploited Vulnerability

CVE-2024-1708

ConnectWise ScreenConnect Path Traversal Vulnerability

ConnectWise ScreenConnect

ConnectWise ScreenConnect 23.9.7 and prior are affected by path-traversal vulnerability, which may allow an attacker the ability to execute remote code or directly impact confidential data or critical systems.

CVSS
8.4
HIGH
EPSS
87.6%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
21 Feb 2024
CWE-22

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 28 April 2026. US federal agencies were required to remediate it by 12 May 2026. CISA records this vulnerability as known to be used in ransomware campaigns.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 87.6%, which is higher than 99.7% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H

Frequently asked questions

Is CVE-2024-1708 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2024-1708.

What does CVE-2024-1708 affect?

CVE-2024-1708 affects ConnectWise ScreenConnect. ConnectWise ScreenConnect 23.9.7 and prior are affected by path-traversal vulnerability, which may allow an attacker the ability to execute remote code or directly impact confidential data or critical systems.

How severe is CVE-2024-1708?

CVE-2024-1708 is rated HIGH with a CVSS base score of 8.4. EPSS puts the probability of exploitation in the next 30 days at 87.6%, higher than 99.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 12 May 2026.

How should organisations respond to CVE-2024-1708?

Apply the vendor patch for ConnectWise ScreenConnect as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.