dbcve.org
SuitecrmApplication

CVE-2026-32697

MEDIUM · 6.5 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 8.9.3 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
SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to versions 8.9.3, the `RecordHandler::getRecord()` method retrieves any record by module and ID without checking the current user's ACL view permission. The companion `saveRecord()` method correctly checks `$bean->ACLAccess('save')`, but `getRecord()` skips the equivalent `ACLAccess('view')` check. Version 8.9.3 patches the issue.

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

The RecordHandler::getRecord() method in SuiteCRM fails to enforce ACL view permissions, allowing any authenticated user to retrieve records they shouldn't have access to by knowing the module name and record ID. Unlike the companion saveRecord() method which properly validates ACLAccess('save'), getRecord() lacks the equivalent ACLAccess('view') check, creating an insecure direct object reference (IDOR) vulnerability leading to unauthorized information disclosure.

MitigationUpgrade to SuiteCRM version 8.9.3 or later, which adds the missing ACL view permission check to the getRecord() method.

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
SuitecrmApplication
Affected:< 8.9.3

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 installed SuiteCRM version
    Access the SuiteCRM admin panel or check the version file (typically in SuiteCRM root directory) to determine the exact version number
    Affected if The installed version is lower than 8.9.3 (for example, 8.9.2, 8.9.1, 8.8.x, etc.)
  2. Locate the RecordHandler class file
    Navigate to the SuiteCRM source code and locate the RecordHandler class - typically in the Core/app directory or similar path under the SuiteCRM installation
    Affected if The RecordHandler::getRecord() method exists in the codebase
  3. Inspect getRecord() method for ACL view check
    Open the RecordHandler class file and examine the getRecord() method implementation to verify whether it contains an ACLAccess('view') or similar permission validation call
    Affected if The getRecord() method lacks any ACLAccess('view') or equivalent permission check, while the saveRecord() method in the same class contains proper ACLAccess('save') validation
  4. Verify ACL enforcement gap through user testing
    Using a test authenticated user account with limited module permissions (for example, a user who cannot view Accounts module records), attempt to access a specific record ID from a restricted module via the getRecord() method or API endpoint
    Affected if The authenticated user can successfully retrieve record details for a module where they have no view permissions, simply by knowing the module name and record ID

A user is affected if their SuiteCRM installation version is below 8.9.3 and the RecordHandler::getRecord() method does not enforce ACL view permissions, allowing unauthorized record access.

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

Upgrade to SuiteCRM version 8.9.3 or later, which adds the missing ACL view permission check to the getRecord() method.

Recommended fix High confidence

8.9.3

  1. Create a complete backup of the SuiteCRM database and all application files
  2. Download SuiteCRM version 8.9.3 or later from the official SuiteCRM website (suitecrm.com) or GitHub releases
  3. Follow the standard SuiteCRM upgrade procedure: upload the new files, run the upgrade wizard, and complete the migration
  4. Clear the SuiteCRM cache by deleting contents of cache/ directory (except .gitkeep)
  5. Log in as an administrator and verify the upgrade was successful by checking the version number in About section
  6. Test that users can only view records they have ACL view permission for, confirming the vulnerability is remediated
Caveat Standard SuiteCRM upgrade precautions apply - always test in staging environment first and review upgrade notes

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

Fix this in Suitecrm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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