CASCACascade Atlas

Evidence dossier

CVE-2025-3935

ScreenConnect Exposure to ASP.NET ViewState Code Injection

61.7–78.9Priority evidence range
As known Jul 19, 2026, 5:00 AM UTCgen-56ccdaf9

Normalized restatement

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.

State
PUBLISHED
Published
Apr 25, 2025
Updated
Feb 26, 2026
Evidence coverage
85%
CISA KEVCatalog member

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

FIRST EPSS3.36%

2026-07-18 · v2026.06.15 · percentile 87.4%

Source stateNo scored conflict

Distinct CVSS assessments remain side by side; none are averaged.

Source comparison

Who said what

CISA-ADPindependent enrichment
container

CISA ADP Vulnrichment

ConnectWiseoriginal assertion
container

ScreenConnect Exposure to ASP.NET ViewState Code Injection

CISA KEVoriginal assertion
observed_exploitation

ConnectWise ScreenConnect Improper Authentication Vulnerability

FIRST EPSSoriginal assertion
model_probability

Probability 0.033610000000; percentile 0.873740000000

Applicability

Cited product scope

Trace impact →
ConnectWiseScreenConnect
[{"status": "affected", "version": "<25.2.3"}]unknown
Unknown vendorUnknown product
cpe:2.3:a:connectwise:screenconnect:*:*:*:*:*:*:*:*; end excluding 25.2.4supported

Assessments

CVSS by origin

7.2
nvd@nist.govCVSS 3.1 · role PrimaryCVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
8.1
7d616e1a-3288-43b1-a0dd-0a65d3e70a49CVSS 3.1 · role SecondaryCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
8.1
ConnectWiseCVSS 3.1 · role unknownCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Limitations and unknowns

  • KEV membership is authoritative for the catalog, not proof of exposure in any environment.
  • EPSS is a dated model probability and not an individual-environment prediction.
  • Affected or fixed status applies only to the exact cited product and version scope; unresolved scope remains unknown.
  • NVD-carried upstream facts remain derivative and are not independent corroboration.
  • Only NVD metrics validated under the generation-bound calculator are Public Priority eligible; direct CVE record metrics remain display-only.
  • NVD CVSS source eligibility is closed: NVD-authored, exact record-source, or registered same-CVE container origin; unmapped sources remain display-only.
  • Factor D is unknown in Public Core because no accepted canonical mapping-obligation ledger is present.
  • Core replay supports the active and immediately prior generation; retrospective valid-at replay is deferred.