Improper limitation of a pathname to a restricted directory (“path traversal”)
Affects self-hosted (on-premise) ScreenConnect 23.9.7 and prior; cloud instances were already remediated. Fixed in 23.9.8, which the vendor says should be applied immediately.
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Listed in CISA KEV
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Actively exploited
- Fix
- Fixed in 23.9.8
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
ConnectWise ScreenConnect, a remote access and support software product, is affected by a path traversal flaw that lets an attacker escape the intended directory and access files they should not reach. Successful exploitation could allow remote code execution, exposure of confidential data, or direct impact on critical systems.
Summarized by anthropic/claude-haiku-5.5. Verify details against the original sources.
Read the original description
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.
Timeline
- CVE published
- Added to CISA KEV
CISA has evidence of exploitation in the wild
- CISA remediation deadline
Due date for US federal agencies to patch
- Record last updated
- EPSS reached 10%
FIRST estimates at least a 10% chance of exploitation in the next 30 days
Affected versions
- ConnectWise ScreenConnect
through 23.9.7
References 2
Questions about CVE-2024-1708
What does this mean?
A path handling flaw in ScreenConnect (a path traversal bug) means file paths are not properly kept within the intended directory. The advisory says it could allow remote code execution or direct impact on confidential data or critical systems.Source: connectwise.com
Am I affected, and how do I check?
ScreenConnect version 23.9.7 and prior, on self-hosted (on-premise) instances. The advisory states ScreenConnect cloud instances were already remediated. Check the installed ScreenConnect version on the server against this range.Source: connectwise.com
What should I do about it?
Update self-hosted ScreenConnect servers to version 23.9.8, which the advisory says contains the patch. No workaround is listed in the facts.Source: connectwise.com
Is it being exploited?
Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2026-04-28, which means it has evidence of attacks. No public exploit code is tracked.Source: cisa.gov, cve.now feed data