dbcve.org
AutomateApplication · Connectwise

CVE-2023-23126

MEDIUM · 6.1 CVSS v3.1 Published 2023-02-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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
Connectwise Automate 2022.11 is vulnerable to Clickjacking. The login screen can be iframed and used to manipulate users to perform unintended actions. NOTE: the vendor's position is that a Content-Security-Policy HTTP response header is present to block this attack.

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

Connectwise Automate 2022.11 login screen can be embedded in an iframe, enabling clickjacking attacks where users are tricked into performing unintended actions through overlaid invisible or disguised UI elements. The vendor claims a Content-Security-Policy exists but the vulnerability persists.

MitigationImplement X-Frame-Options: DENY or SAMEORIGIN header, or configure CSP frame-ancestors directive to prevent the login page from being iframed by untrusted origins.

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
AutomateApplication
Affected:= 2022.11

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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. Verify Connectwise Automate version
    Check the installed version of Connectwise Automate by reviewing the application dashboard, About section, or checking the installation directory for version information. Compare against the affected version 2022.11.
    Affected if The installed version is exactly 2022.11
  2. Inspect X-Frame-Options HTTP header on login page
    Use browser developer tools or a command-line tool like curl to fetch the login page URL and inspect the response headers. Look for the X-Frame-Options header.
    Affected if X-Frame-Options header is missing, set to ALLOW-FROM (deprecated), or not present in the response headers
  3. Inspect Content-Security-Policy header on login page
    Examine the Content-Security-Policy HTTP header in the login page response. Look specifically for the frame-ancestors directive.
    Affected if CSP header is missing, does not include frame-ancestors directive, or frame-ancestors allows arbitrary origins (such as using wildcard or missing restrictions)
  4. Verify iframe embeddability (manual test)
    Create a simple HTML page with an iframe pointing to the Connectwise Automate login URL. Open this page in a browser and confirm whether the login page renders inside the iframe.
    Affected if The login page successfully loads inside the iframe without being blocked

A user is affected if they have Connectwise Automate version 2022.11 installed AND the login page can be embedded in an iframe due to missing or ineffective X-Frame-Options and CSP frame-ancestors protections.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement X-Frame-Options: DENY or SAMEORIGIN header, or configure CSP frame-ancestors directive to prevent the login page from being iframed by untrusted origins.

Recommended fix Moderate confidence
  1. 1. Verify the current Content-Security-Policy HTTP response header on the ConnectWise Automate login page
  2. 2. If CSP header is missing or incomplete, add or modify the CSP header to include 'frame-ancestors' directive
  3. 3. Configure the CSP header with 'frame-ancestors \'none\'' to prevent all framing, or specify trusted domains if framing is required
  4. 4. Apply the CSP header configuration to the web server (IIS, Apache, or nginx) hosting ConnectWise Automate
  5. 5. Test the configuration by attempting to iframe the login page from an unauthorized domain
  6. 6. Verify the CSP header is being applied correctly using browser developer tools or curl -I command

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

Fix this in Automate Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-23126 — 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-2023-23126 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