Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-32697: CWE-639: Authorization Bypass Through User-Controlled Key in SuiteCRM SuiteCRM-Core

0
Medium
VulnerabilityCVE-2026-32697cvecve-2026-32697cwe-639
Published: Thu Mar 19 2026 (03/19/2026, 23:13:08 UTC)
Source: CVE Database V5
Vendor/Project: SuiteCRM
Product: SuiteCRM-Core

Description

CVE-2026-32697 is an authorization bypass vulnerability in SuiteCRM-Core versions prior to 8. 9. 3. The issue arises because the getRecord() method does not verify the current user's permission to view a record, allowing users with limited privileges to access records they should not see. Although the saveRecord() method correctly enforces save permissions, the missing view permission check in getRecord() enables unauthorized data access. This vulnerability has a CVSS score of 6. 5, indicating medium severity, and does not require user interaction but does require some level of privileges. The vulnerability was patched in version 8. 9. 3.

AI-Powered Analysis

AILast updated: 03/19/2026, 23:39:38 UTC

Technical Analysis

The vulnerability CVE-2026-32697 affects SuiteCRM-Core, an open-source CRM platform widely used by enterprises for customer data management. Specifically, the flaw exists in the RecordHandler::getRecord() method, which retrieves records by module and ID. In versions prior to 8.9.3, this method fails to enforce Access Control List (ACL) view permissions, allowing authenticated users with limited privileges to bypass authorization controls and access records they should not be able to view. This contrasts with the saveRecord() method, which correctly checks for save permissions using $bean->ACLAccess('save'). The lack of an equivalent ACLAccess('view') check in getRecord() means that users can retrieve sensitive data without proper authorization. The vulnerability is categorized under CWE-639 (Authorization Bypass Through User-Controlled Key). The CVSS v3.1 base score of 6.5 reflects a medium severity due to the high confidentiality impact, network attack vector, low attack complexity, and requiring privileges but no user interaction. The vulnerability was publicly disclosed on March 19, 2026, and patched in SuiteCRM version 8.9.3. No known exploits have been reported in the wild, but the flaw poses a significant risk of unauthorized data disclosure if left unpatched.

Potential Impact

This vulnerability can lead to unauthorized disclosure of sensitive customer and business data stored within SuiteCRM instances. Attackers or unauthorized users with limited privileges can exploit this flaw to view records they should not have access to, potentially exposing confidential information such as customer contacts, sales data, and internal notes. This breach of confidentiality can damage organizational reputation, violate data privacy regulations, and lead to competitive disadvantages. Since SuiteCRM is often integrated with other business systems, unauthorized data access could facilitate further attacks or data leakage. The vulnerability does not affect data integrity or availability directly but compromises the confidentiality of CRM data. Organizations relying on SuiteCRM for customer relationship management are at risk, especially if they have not applied the patch or are running older versions. The medium severity rating suggests a moderate but significant risk, particularly in environments with sensitive or regulated data.

Mitigation Recommendations

The primary mitigation is to upgrade SuiteCRM-Core to version 8.9.3 or later, where the authorization bypass issue in getRecord() has been fixed by adding proper ACL view permission checks. Until the upgrade can be performed, organizations should restrict access to SuiteCRM to trusted users only and implement network-level controls such as VPNs or IP whitelisting to limit exposure. Additionally, review and tighten user roles and permissions within SuiteCRM to minimize the number of users with access to sensitive modules. Monitoring and logging access to CRM records can help detect unusual access patterns indicative of exploitation attempts. If upgrading immediately is not feasible, consider applying custom patches or workarounds to enforce ACL checks in the getRecord() method. Regularly audit SuiteCRM instances for outdated versions and ensure patch management processes include this critical update. Finally, educate users about the importance of least privilege principles to reduce the risk of internal misuse.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-13T14:33:42.822Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69bc85a4e32a4fbe5f07b2e0

Added to database: 3/19/2026, 11:24:20 PM

Last enriched: 3/19/2026, 11:39:38 PM

Last updated: 3/20/2026, 1:32:32 AM

Views: 3

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses