basicsecurity.net
Proof, not just disclosure.
Threats / ConnectWise / CVE-2024-1708
CVE-2024-1708 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-07

ConnectWise ScreenConnect vulnerability

ConnectWise ScreenConnect contains a path traversal vulnerability (CWE-22) enabling remote code execution and unauthorized access to sensitive data. Active exploitation and ransomware campaigns documented.

Verdict

Today item, not a backlog item.

Critical remote code execution vulnerability in widely deployed remote access software. Path traversal flaw permits attackers to bypass access controls, execute arbitrary code, and compromise confidential systems. High exploitation activity and ransomware integration confirm severe operational risk.

CISA KEV Yes · 2026-04-283Ransomware use Flagged3EPSS 0.8481 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-04-28), flagged for known ransomware use.
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.8481 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
FIRST EPSS ↗High
Severity / affected
Affected: ConnectWise, ScreenConnect. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-22 Path Traversal — weakness family: Path traversal / file.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-22 · Path TraversalPath traversal / file
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No threat-actor attribution is established from the public feed for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious request using path traversal sequences to bypass directory restrictions and access files outside intended boundaries.
Business
Attacker gains unauthorized file system access to ScreenConnect installation, exposing configuration files and credentials.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I leverage the traversal access to read or modify executable files and scripts executed by the ScreenConnect service.
Business
Remote code execution achieved with service-level privileges, enabling full system compromise.
3

Lateral reach — past segmentation narrative 3

Attacker
I establish persistent access and deploy ransomware payloads across the victim environment using ScreenConnect's trusted network position.
Business
Critical systems encrypted, operations halted, ransom demanded. Lateral movement to connected infrastructure accelerates damage scope.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • Ransomware-use flag (CISA)
  • EPSS probability (FIRST)
  • CWE weakness mapping (NVD)
  • Catalogued by cisa-cg (CNA)

    • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
    • Disclosure & credit2
    Catalogued by cisa-cgCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.