dbcve.org
SuitecrmApplication

CVE-2026-29189

HIGH · 8.1 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 7.15.1 / 8.9.3 or later.
See remediation →
87/100
Remediation priority · High
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 7.15.1 and 8.9.3, the SuiteCRM REST API V8 has missing ACL (Access Control List) checks on several endpoints, allowing authenticated users to access and manipulate data they should not have permission to interact with. Versions 7.15.1 and 8.9.3 patch 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

SuiteCRM REST API V8 has missing ACL (Access Control List) checks on several endpoints, allowing authenticated users to bypass authorization controls and access or manipulate data outside their permitted scope.

MitigationUpgrade SuiteCRM to version 7.15.1 or 8.9.3 or later to patch the missing ACL checks in the REST API V8 endpoints.

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:< 7.15.1>= 8.0.0, < 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
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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
    Locate the version file or admin panel in your SuiteCRM installation. Typically found in the About section of the admin panel or in a version.php file in the root directory.
    Affected if The installed version is less than 7.15.1, or greater than or equal to 8.0.0 but less than 8.9.3.
  2. Verify REST API V8 module is enabled
    Check the SuiteCRM administration panel under API settings or examine the API configuration files to confirm the REST API V8 endpoint is active.
    Affected if REST API V8 is enabled and the version falls within the affected ranges.
  3. Check ACL module configuration status
    Navigate to the ACL (Access Control List) settings in the SuiteCRM admin panel and verify that role-based access controls are properly defined for user accounts.
    Affected if ACL roles exist but the REST API V8 endpoints are not enforcing them correctly.
  4. Review API endpoint access logs
    Examine SuiteCRM API access logs or server access logs for API V8 calls. Look for requests from authenticated users accessing endpoints outside their defined role permissions.
    Affected if Authenticated users are making API calls to endpoints not assigned to their role.

You are affected if your SuiteCRM version is 7.x before 7.15.1 or 8.x before 8.9.3, and the REST API V8 is enabled with users having API 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 7.15.1 / 8.9.3 or later
Fixed in 7.15.18.9.3
Interim mitigation

Upgrade SuiteCRM to version 7.15.1 or 8.9.3 or later to patch the missing ACL checks in the REST API V8 endpoints.

Recommended fix High confidence

SuiteCRM 7.15.1 for 7.x line; SuiteCRM 8.9.3 for 8.x line

  1. 1. Identify your current SuiteCRM version by checking the admin panel or the version.php file in the installation root.
  2. 2. If running SuiteCRM 7.x versions prior to 7.15.1, plan upgrade to version 7.15.1.
  3. 3. If running SuiteCRM 8.x versions prior to 8.9.3, plan upgrade to version 8.9.3.
  4. 4. Before upgrading, perform a complete backup of the database and all application files.
  5. 5. Review the upgrade documentation at docs.suitecrm.com for your specific version path.
  6. 6. Execute the upgrade following official upgrade procedures, testing in a staging environment first.
  7. 7. After upgrade, verify that REST API ACL controls are functioning correctly by testing access to restricted endpoints.

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

Fix this in Suitecrm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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