CVE-2026-0695
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 · uneditedIn ConnectWise PSA versions older than 2026.1, Time Entry notes stored in the Time Entry Audit Trail may be rendered without applying output encoding to certain content. Under specific conditions, this may allow stored script code to execute in the context of a user’s browser when the affected content is displayed.
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 · high confidenceA stored cross-site scripting (XSS) vulnerability exists in ConnectWise PSA versions prior to 2026.1. Time Entry notes stored in the Time Entry Audit Trail are rendered without proper output encoding, allowing malicious JavaScript or other script code to execute in a user's browser when the affected audit trail content is displayed.
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< 2026.1CVSS 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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Check installed ConnectWise PSA versionLog into the ConnectWise PSA administrative interface and navigate to System > Setup > System Administration or Help > About. Alternatively, check the installation directory for a version file or query the database for the system information table containing the version number.Affected if The installed version is any release prior to 2026.1 (for example, 2025.x, 2024.x, or earlier)
-
Verify Time Entry module is accessibleNavigate to Time > Time Entries or look for Time Entry-related menu items in the PSA interface. Confirm the Time Entry functionality is enabled for your organization.Affected if The Time Entry module is enabled and users have access to create or view time entries
-
Check Time Entry Audit Trail accessLocate the Audit Trail feature within the Time Entry section. This may be found under Time > Reporting > Audit Trail or within individual time entry records. Verify that users can view historical time entry records.Affected if The Time Entry Audit Trail feature is accessible and displays historical time entry records including notes
-
Identify if custom output encoding is appliedInspect the web application response when viewing Time Entry Audit Trail notes. Check for HTML-encoded characters (for example, <script> instead of <script>, & instead of &) in the displayed notes.Affected if Notes containing special characters appear as raw HTML/JavaScript without encoding (for example, <script> appears as <script> rather than <script>)
You are affected if your ConnectWise PSA version is prior to 2026.1 AND the Time Entry Audit Trail feature is accessible, as notes are rendered without proper output encoding allowing script execution.
Generated from the published advisory. Verify against your own configuration.
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 · scoped2026.1
Upgrade ConnectWise PSA to version 2026.1 or later which implements proper output encoding for Time Entry notes in the audit trail.
2026.1
- Upgrade ConnectWise PSA to version 2026.1 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-0695 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-0695 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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