CVE-2025-32975
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 · uneditedQuest KACE Systems Management Appliance (SMA) 13.0.x before 13.0.385, 13.1.x before 13.1.81, 13.2.x before 13.2.183, 14.0.x before 14.0.341 (Patch 5), and 14.1.x before 14.1.101 (Patch 4) contains an authentication bypass vulnerability that allows attackers to impersonate legitimate users without valid credentials. The vulnerability exists in the SSO authentication handling mechanism and can lead to complete administrative takeover.
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 confidenceQuest KACE SMA contains an authentication bypass in its SSO authentication handling mechanism. Attackers can impersonate legitimate users without valid credentials by exploiting this flaw, enabling complete administrative account takeover of the appliance.
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>= 13.0, < 13.0.385>= 13.1, < 13.1.81>= 13.2, < 13.2.183>= 14.0, < 14.0.341>= 14.1, < 14.1.101CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
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.
-
Determine KACE appliance versionLog into the KACE admin web interface and navigate to the System Overview or System Information page. Alternatively, check the appliance's about section or run the command 'select * from app_version' against the KACE database if direct database access is available.Affected if The installed version falls within any of these ranges: 13.0 through 13.0.384, 13.1 through 13.1.80, 13.2 through 13.2.182, 14.0 through 14.0.340, or 14.1 through 14.1.100.
-
Verify if SSO authentication is enabledIn the KACE admin interface, go to Settings > Authentication or Security Settings and check whether Single Sign-On (SSO) authentication methods such as SAML, OAuth, or LDAP integration are configured and active.Affected if SSO authentication is enabled and the appliance version is in the affected ranges listed above.
-
Inspect SSO configuration for anomaliesReview the SSO provider configuration under the Authentication settings. Look for unexpected entries, modified Assertion Consumer Service URLs, or changes to identity provider certificates that were not initiated by an administrator.Affected if SSO is enabled and configuration shows unauthorized modifications or unexpected provider settings.
-
Review authentication logs for suspicious activityAccess the KACE system logs or authentication audit logs, typically found under Logs > System Logs or Security Logs. Search for failed login attempts followed by successful administrative actions from unfamiliar IP addresses or outside expected business hours.Affected if Authentication logs show successful administrative sessions originating from IP addresses not associated with legitimate SSO users.
You are affected if your KACE appliance runs any version from 13.0 through 13.0.384, 13.1 through 13.1.80, 13.2 through 13.2.182, 14.0 through 14.0.340, or 14.1 through 14.1.100 AND has SSO authentication enabled.
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 · scoped13.0.38513.1.8113.2.183
Apply vendor patches: upgrade to 13.0.385+, 13.1.81+, 13.2.183+, 14.0.341 (Patch 5)+, or 14.1.101 (Patch 4)+ per the affected version branch.
Upgrade to 13.0.385, 13.1.81, 13.2.183, or 14.0.341 depending on your current version branch (or 14.1.101 if on 14.1.x)
- 1. Identify the current installed version of KACE Systems Management Appliance via the admin console or system information
- 2. Determine which version branch your current installation belongs to (13.0.x, 13.1.x, 13.2.x, or 14.0.x)
- 3. Schedule a maintenance window for the upgrade procedure
- 4. Create a complete backup of the KACE SMA configuration and database
- 5. Download the appropriate patched release from Quest support portal: upgrade to 13.0.385 for 13.0.x branch, 13.1.81 for 13.1.x branch, 13.2.183 for 13.2.x branch, or 14.0.341 for 14.0.x branch
- 6. Apply the upgrade following Quest's standard upgrade documentation
- 7. After upgrade completes, verify the system is operational and accessible
- 8. Confirm SSO authentication is functioning correctly for all users
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-32975 — 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-2025-32975 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