Vulnerability report

Exploitation attempts observed in the wild Confirmed confidence In CISA KEV

CVE-2025-3935

ScreenConnect Exposure to ASP.NET ViewState Code Injection

ConnectWise / ScreenConnect · <25.2.3

Severity
CVSS 8.1 · High
Confidence
Confirmed
Exploit status
Exploitation attempts observed in the wild
EPSS
3.6%
First observed
—
Last observed
—

Decision summary

What security teams need to know first

Direct answers before the deeper technical record.

What it is

CVE-2025-3935 is an unauthenticated ScreenConnect Exposure to ASP.NET ViewState Code Injection. ScreenConnect versions 25.2.3 and earlier versions may be susceptible to a ViewState code injection attack. ASP.NET Web...

Have exploitation attempts been observed?

Yes. Exploitation attempts have been reported for this vulnerability. Previdian lists it as a known exploited vulnerability. Listed in CISA KEV. Also reported by third-party sources. Confidence is confirmed.

Who is affected?

ConnectWise / ScreenConnect <25.2.3.

What should we do?

Prioritize remediation. Validate affected assets and apply vendor fixes on an accelerated timeline.

Overview

ScreenConnect versions 25.2.3 and earlier versions may be susceptible to a ViewState code injection attack

ScreenConnect versions 25.2.3 and earlier versions may be susceptible to a ViewState code injection attack. ASP.NET Web Forms use ViewState to preserve page and control state, with data encoded using Base64 protected by machine keys.  It is important to note that to obtain these machine keys, privileged system level access must be obtained.

If these machine keys are compromised, attackers could create and send a malicious ViewState to the website, potentially leading to remote code execution on the server. 

The risk does not originate from a vulnerability introduced by ScreenConnect, but from platform level behavior.  This had no direct impact to ScreenConnect Client. ScreenConnect 2025.4 patch disables ViewState and removes any dependency on it.

ConnectWise Affected
ScreenConnect
<25.2.3
Published
25 Apr 2025
Exploitation Attempts Reported
01 Jun 2026
Attack vector
Remote
Complexity
High
Privileges
None
User interaction
None

Tags

cisa dotnet

CVE References

Exploitation evidence

Evidence of exploitation attempts

Third-party attestation and first-party sensor observation are shown separately so teams can judge the evidence chain.

Exploitation attempts observed in the wild

CVE

Recorded 01 Jun 2026

A trusted third party reported exploitation attempts.

Known exploited vulnerability sources

Per-source evidence links for KEV attestations are available through the Previdian Pro API.

Learn about Pro API access
Source Added
CVE First 2026-06-01 10:31 UTC
CISA 2026-06-02 14:07 UTC

Detection

Operational artifacts and observed signals

Make the evidence actionable in scanner, SOC, and edge-control workflows.

Scanner coverage

No scanner integrations recorded yet.

Virtual patch status

No Previdian virtual patch is currently available. Future rules ship for ModSecurity, Cloudflare, and AWS WAF.

Learn about virtual patches →

No detection artifacts or sensor request patterns are available for this CVE yet.

Check back as sensor telemetry and scanner integrations are updated.

Risk and context

Severity, weaknesses, and research context

CVSS v3.1

8.1 High

Potential damage if exploited. Separate from whether attackers are using it.

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

EPSS

3.6%

Estimated chance of exploitation in the next 30 days. Previdian's warning comes from evidence, not this score.

Timeline

From disclosure to observed exploitation attempts

  1. 14:07 UTC

    Added to CISA KEV

    Listed in the CISA Known Exploited Vulnerabilities catalog

  2. 10:31 UTC

    Added to Previdian KEV Feed

    High-confidence, third-party report of exploitation attempts

  3. 18:27 UTC

    CVE published

    Vulnerability disclosed publicly

  4. 14:32 UTC

    CVE ID reserved

    Identifier reserved by the CNA

Pro API

Automate this intelligence

Confidence, exploit status, sensor telemetry, PoCs, scanner integrations, mentions, and tags are available programmatically for VM, SOC, and CTI workflows.

  • Evidence confidence and provenance
  • First-party sensor telemetry
  • PoC and scanner references
  • Affected versions and enrichment
  • Automation-ready JSON delivery

GET /api/v2/pro/kevs/CVE-2025-3935

Sample API response
{
  "cve_id": "CVE-2025-3935",
  "confidence": "Confirmed",
  "cvss_score": 8.1,
  "cvss_estimated": false,
  "epss_score": 0.03597,
  "exploit_status": {
    "exploited_in_the_wild": true,
    "active_exploitation_observed": false
  },
  "sensor_telemetry": { "attempts": 0, "sensors": 0 }
}