dbcve.org
SuitecrmApplication

CVE-2026-29101

HIGH · 7.5 CVSS v3.1 Published 2026-03-19
Fix available
A fix is available. Upgrade to 7.15.1 / 8.9.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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, a Denial-of-Service (DoS) vulnerability exists in SuiteCRM modules. 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 · moderate confidence

A Denial-of-Service (DoS) vulnerability exists in SuiteCRM modules affecting versions prior to 7.15.1 and 8.9.3. The vulnerability can be exploited to cause service disruption, as indicated by the HIGH CVSS score of 7.5.

MitigationUpgrade SuiteCRM to version 7.15.1 or 8.9.3 or later to patch the DoS vulnerability.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Check SuiteCRM version via admin interface
    Log in as administrator and navigate to Admin > About SuiteCRM, or look for a version display in the application footer or help/about section
    Affected if The displayed version falls below 7.15.1 or is 8.x but below 8.9.3
  2. Locate SuiteCRM version file
    Access the SuiteCRM installation directory and open the file /suitecrm/version.php (or /public/legacy/version.php for 8.x installations). Read the $sugar_version variable
    Affected if The version number in the file is < 7.15.1 or >= 8.0.0 but < 8.9.3
  3. Check composer.json version
    If available, examine the composer.json file in the SuiteCRM root directory for the suitecrm/suitecrm version entry
    Affected if The listed version is < 7.15.1 or >= 8.0.0 but < 8.9.3
  4. Query database for version
    Connect to the SuiteCRM database and run: SELECT value FROM config WHERE category = 'system' AND name = 'suitecrm_version'
    Affected if The returned version value is < 7.15.1 or >= 8.0.0 but < 8.9.3

Your environment is affected if SuiteCRM version is below 7.15.1 (7.x branch) or between 8.0.0 and 8.9.3 (8.x branch).

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 DoS vulnerability.

Recommended fix High confidence

SuiteCRM 7.15.1 (for 7.x line) or SuiteCRM 8.9.3 (for 8.x line)

  1. 1. Create a complete backup of the SuiteCRM database and all application files
  2. 2. Enable maintenance mode or take the site offline to prevent user access during upgrade
  3. 3. For SuiteCRM 7.x users: Download version 7.15.1 from the official SuiteCRM repository
  4. 4. For SuiteCRM 8.x users: Download version 8.9.3 from the official SuiteCRM repository
  5. 5. Extract the new version and replace the existing files, preserving custom configurations in config.php and any custom modules
  6. 6. Clear the cache directory (cache/) to ensure new files are loaded
  7. 7. Run the repair and rebuild functions via Admin > Repair > Quick Repair and Rebuild
  8. 8. Verify the upgrade by logging in and checking that all modules function correctly
Caveat Standard upgrade precautions apply; test in staging environment first; ensure PHP version compatibility for the target release

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

Fix this in Suitecrm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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