dbcve.org
Professional Service AutomationApplication · Connectwise

CVE-2025-7204

MEDIUM · 6.5 CVSS v3.1 Published 2025-07-09
Fix available
A fix is available. Upgrade to 2025.9 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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 ConnectWise PSA versions older than 2025.9, a vulnerability exists where authenticated users could gain access to sensitive user information. Specific API requests were found to return an overly verbose user object, which included encrypted password hashes for other users. Authenticated users could then retrieve these hashes.  An attacker or privileged user could then use these exposed hashes to conduct offline brute-force or dictionary attacks. Such attacks could lead to credential compromise, allowing unauthorized access to accounts, and potentially privilege escalation within the system.

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 confidence

ConnectWise PSA versions before 2025.9 contain an information disclosure vulnerability where authenticated API requests return overly verbose user objects that include encrypted password hashes for other users. Authenticated attackers can retrieve these hashes and conduct offline brute-force or dictionary attacks to compromise credentials.

MitigationUpgrade to ConnectWise PSA version 2025.9 or later, and audit API response schemas to ensure password hashes and other sensitive fields are excluded from user object responses.

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
Professional Service AutomationApplication
Affected:< 2025.9

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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. Identify ConnectWise PSA version
    Locate the installed ConnectWise PSA version in the system administration panel or product information screen. This is typically found under Help > About or in the version information displayed on the login page.
    Affected if The installed version is any release before 2025.9 (e.g., 2025.8, 2025.7, earlier major versions).
  2. Verify API access is enabled
    Check if the REST API feature is enabled in ConnectWise PSA. Navigate to System > Setup > Integrations or the API configuration section, and confirm whether API access is permitted for authenticated users.
    Affected if API access is enabled and available to authenticated users, allowing them to make API requests.
  3. Inspect user object API responses
    Using an authenticated API client (such as Postman or curl with valid credentials), query the user endpoints (e.g., GET /api/v3_2/users or /api/v3_2/contacts). Examine the JSON response body for user records.
    Affected if The API responses return user objects containing password hash fields (look for fields named passwordHash, encryptedPassword, pwdHash, or similar variations).
  4. Confirm hash presence in other-user responses
    After authenticating as a standard user (non-admin), query the user API endpoint to retrieve the full list of user objects. Verify whether the response includes encrypted password hashes for users other than the currently authenticated user.
    Affected if Password hashes for other users are visible in API responses obtained with your own authenticated session.

Your environment is affected if ConnectWise PSA version is below 2025.9 and the API returns encrypted password hashes for users in the response objects.

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 2025.9 or later
Fixed in 2025.9
Interim mitigation

Upgrade to ConnectWise PSA version 2025.9 or later, and audit API response schemas to ensure password hashes and other sensitive fields are excluded from user object responses.

Recommended fix High confidence

2025.9

  1. 1. Identify the current ConnectWise PSA version by accessing the system admin panel or checking the software documentation
  2. 2. Review the ConnectWise PSA 2025.9 release notes to confirm the security fixes address the information exposure vulnerability
  3. 3. Create a complete backup of the current ConnectWise PSA database and configuration
  4. 4. Schedule a maintenance window for the upgrade process
  5. 5. If available, test the upgrade in a non-production/staging environment first
  6. 6. Upgrade ConnectWise PSA to version 2025.9 or later following the official upgrade documentation
  7. 7. After upgrade, verify the fix by making API requests that previously returned verbose user objects and confirm password hashes are no longer exposed
  8. 8. Monitor system logs for any unusual activity following the upgrade

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

Fix this in Professional Service Automation Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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