VulnerabilityPublished 19 Mar 2026Updated 21 Mar 2026

CVE-2026-29108: SuiteCRM-Core · Information Exposure

Affects SuiteCRM-CoreSource CVE Database V5

Compare

Not known to be exploited · CVSS 6.5 Medium : upgrade to 8.9.3 when convenient.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 24% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 8.9.3

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 19 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade SuiteCRM-Core and suitecrm/SuiteCRM-Core to 8.9.3.

Affected software

Product	Affected	Fixed in
SuiteCRMSuiteCRM-Core	Affected <8.9.3	Fixed in 8.9.3
GitHubsuitecrm/SuiteCRM-Core`pkg:github/suitecrm/SuiteCRM-Core`Other threats	Affected <8.9.3	Fixed in 8.9.3

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade SuiteCRM-Core to version 8.9.3 or later to remediate this vulnerability. In addition to patching, it is critical to enforce strong password policies to reduce the risk of successful password cracking. Implementing account lockout mechanisms and monitoring for unusual API access patterns can help detect exploitation attempts. Restrict API access to trusted users and consider network segmentation to limit exposure of the CRM system. Regularly audit user accounts and MFA configurations to ensure no unauthorized changes have occurred. Employ logging and alerting on API calls that request user information to identify suspicious activity early. Finally, educate users about the importance of MFA and encourage the use of robust authentication methods to mitigate risks stemming from credential exposure.

Description

SuiteCRM is an open-source, enterprise-ready Customer Relationship Management (CRM) software application. Prior to versions 8.9.3, an authenticated API endpoint allows any user to retrieve detailed information about any other user, including their password hash, username, and MFA configuration. As any authenticated user can query this endpoint, it's possible to retrieve and potentially crack the passwords of administrative users. Version 8.9.3 patches the issue.

Impact

The primary impact of this vulnerability is the compromise of user credential confidentiality within affected SuiteCRM deployments. Attackers can leverage any valid user account to extract password hashes and MFA details of administrative and other privileged users, significantly increasing the risk of privilege escalation and unauthorized system access. Successful password cracking could lead to full account takeover, data exfiltration, manipulation of CRM data, and disruption of business operations. Organizations relying on SuiteCRM for customer data management face reputational damage, regulatory compliance issues, and potential financial losses if attackers exploit this vulnerability. Since SuiteCRM is used globally across various industries, the scope of impact is extensive, particularly for organizations that have not applied the patch or use weak password policies. The vulnerability does not directly affect system availability or data integrity but indirectly threatens these through potential unauthorized access.

Summary

SuiteCRM, an open-source CRM platform widely used by enterprises, contains a vulnerability identified as CVE-2026-29108 affecting versions prior to 8.9.3. The flaw resides in an authenticated API endpoint that improperly exposes sensitive user information to any authenticated user. Specifically, this endpoint allows retrieval of detailed data including password hashes, usernames, and MFA configuration details of other users within the system. Because the endpoint is accessible with standard user credentials, an attacker with any valid account can enumerate users and harvest password hashes. These hashes can then be subjected to offline brute-force or dictionary attacks to recover plaintext passwords, especially if weak passwords are used. The exposure of MFA configuration data further aids attackers in bypassing or targeting multi-factor protections. The vulnerability impacts confidentiality severely but does not affect data integrity or system availability. No user interaction beyond authentication is required, and the attack surface is broad given the common use of SuiteCRM in enterprise environments. The issue was addressed and patched in SuiteCRM version 8.9.3, which restricts access to sensitive user data through the API. No known exploits have been reported in the wild as of the publication date.

CWE-200Exposure of Sensitive Information to an Unauthorized Actor (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #20OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information.
MITRE discourages mapping vulnerabilities to this broad entry; the root cause is usually a more specific weakness.
Architecture and Design · Separation of Privilege
Compartmentalize the system to have "safe" areas where trust boundaries can be unambiguously drawn. Do not allow sensitive data to go outside of the trust boundary and always be careful when interfacing with a compartment outside of the safe area.
OWASP Cheat Sheets
Error Handling (opens in a new tab)
Logging (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.4 (opens in a new tab)
V14.3.3 (opens in a new tab)
V7.3.3 (opens in a new tab)
Attack patterns
Subverting Environment Variable Values (opens in a new tab)
ICMP Echo Request Ping (opens in a new tab)
TCP SYN Scan (opens in a new tab)
Enumerate Mail Exchange (MX) Records (opens in a new tab)
DNS Zone Transfers (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

github.com/SuiteCRM/SuiteCRM-Core/security/advisories/GHSA-xc8w-xc9v-45w5 (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 27 Mar 2026, 19:29 UTC

WeaknessesCWE-200

Technical details

References

Community reviews

Related threats