dbcve.org
ScreenconnectApplication · Connectwise

CVE-2025-14823

MEDIUM · 5.3 CVSS v3.1 Published 2025-12-18
Fix available
A fix is available. Upgrade to 1.0.12 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
In deployments using the ScreenConnect™ Certificate Signing Extension, encrypted configuration values including an Azure Key Vault-related key, could be returned to unauthenticated users through a client-facing endpoint under certain conditions. The values remained encrypted and securely stored at rest; however, an encrypted representation could be exposed in client responses. Updating the Certificate Signing Extension to version 1.0.12 or higher ensures configuration handling occurs exclusively on the server side, preventing encrypted values from being transmitted to or rendered by client-side components.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Certificate Signing Extension in ScreenConnect exposes encrypted configuration values (including Azure Key Vault keys) to unauthenticated users through client-facing endpoints under certain conditions. While the values remain encrypted at rest, their encrypted representation is transmitted to client-side components, potentially aiding further attacks.

MitigationUpdate the Certificate Signing Extension to version 1.0.12 or higher to ensure configuration handling occurs exclusively on the server side and prevent encrypted values from being transmitted to clients.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ScreenconnectApplication
Affected:< 1.0.12

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm ScreenConnect installation and version
    Locate the ScreenConnect installation directory and check the version information, typically found in the application itself or in installation logs
    Affected if The installed version is earlier than 1.0.12
  2. Identify Certificate Signing Extension
    Access the ScreenConnect admin interface and navigate to the Extensions or Plugins section to list installed extensions
    Affected if The Certificate Signing Extension is present in the list of installed extensions
  3. Verify extension version
    Within the Extension details in the admin interface, check the version number of the Certificate Signing Extension
    Affected if The extension version is earlier than 1.0.12
  4. Confirm client-facing endpoint accessibility
    Determine if the ScreenConnect web interface is exposed to unauthenticated or client-facing access by reviewing network configuration and access controls
    Affected if The ScreenConnect client portal is accessible without authentication or to unauthenticated users
  5. Inspect for exposed encrypted values
    Use a browser or HTTP tool to access client-facing endpoints and examine responses for encrypted configuration strings that may contain Azure Key Vault keys or similar sensitive values
    Affected if Encrypted configuration values appear in client-facing HTTP responses

You are affected if ScreenConnect version is earlier than 1.0.12, the Certificate Signing Extension is installed, and client-facing endpoints are accessible to unauthenticated users.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 1.0.12 or later
Fixed in 1.0.12
Interim mitigation

Update the Certificate Signing Extension to version 1.0.12 or higher to ensure configuration handling occurs exclusively on the server side and prevent encrypted values from being transmitted to clients.

Recommended fix High confidence

ScreenConnect Certificate Signing Extension version 1.0.12 or higher

  1. 1. Identify the current version of the ScreenConnect Certificate Signing Extension installed in your environment.
  2. 2. Navigate to the official ConnectWise/ConnectWise website (www.connectwise.com) or the official ScreenConnect download portal.
  3. 3. Download the Certificate Signing Extension version 1.0.12 or higher.
  4. 4. Back up your current ScreenConnect configuration and any related extension configurations.
  5. 5. Install or apply the Certificate Signing Extension version 1.0.12 or higher following the standard extension upgrade procedure.
  6. 6. Verify the upgrade was successful by confirming the extension version displays 1.0.12 or higher in the ScreenConnect administration interface.
  7. 7. Test the client-facing endpoints to confirm encrypted configuration values are no longer exposed in client responses.

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Screenconnect Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-14823 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-14823 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data