dbcve.org
SuitecrmApplication

CVE-2026-29097

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. Versions prior to 7.15.1 and 8.9.3 contain a Server-Side Request Forgery (SSRF) vulnerability combined with a Denial of Service (DoS) condition in the RSS Feed Dashlet component. 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

This is a Server-Side Request Forgery (SSRF) vulnerability combined with a Denial of Service (DoS) condition in the RSS Feed Dashlet component of SuiteCRM. An attacker can potentially make the server perform requests to arbitrary URLs (SSRF) and cause service disruption (DoS) through the RSS Feed Dashlet.

MitigationUpgrade SuiteCRM to version 7.15.1 or 8.9.3 or later to patch this vulnerability. If upgrading is not immediately possible, consider disabling or restricting the RSS Feed Dashlet until the patch can be applied.

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. Determine installed SuiteCRM version
    Access the SuiteCRM About page (usually at /index.php?action=About) or check the version.php file in the SuiteCRM root directory
    Affected if The version is below 7.15.1, or is 8.0.0 through 8.9.2 (8.9.3 and later are patched)
  2. Verify if RSS Feed Dashlet is accessible
    Check if the RSS Feed Dashlet module exists and is not disabled in the SuiteCRM module loader or admin panel under Dashlet configuration
    Affected if The RSS Feed Dashlet is available and can be added to a dashboard by users
  3. Check user permissions for Dashlets
    Review the SuiteCRM roles and ACL settings to determine which users can add or configure the RSS Feed Dashlet
    Affected if Regular users (non-admin) have permission to add and configure dashlets
  4. Inspect RSS Dashlet configuration storage
    Look for saved dashlet configurations in the database table (typically dashlets table) or config files that reference the RSS Feed Dashlet
    Affected if There are active RSS Feed Dashlet configurations present in the system

A user is affected if their SuiteCRM version is below 7.15.1 or between 8.0.0 and 8.9.2 AND the RSS Feed Dashlet is enabled and accessible to users who could trigger the SSRF/DoS condition.

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 this vulnerability. If upgrading is not immediately possible, consider disabling or restricting the RSS Feed Dashlet until the patch can be applied.

Recommended fix High confidence

Upgrade to SuiteCRM 7.15.1 (if on 7.x) or SuiteCRM 8.9.3 (if on 8.x)

  1. 1. Create a complete backup of your SuiteCRM database and all files/directories
  2. 2. Place your SuiteCRM instance into maintenance mode or take it offline
  3. 3. Download the appropriate fixed version: SuiteCRM 7.15.1 (for 7.x installations) or SuiteCRM 8.9.3 (for 8.x installations) from the official SuiteCRM download repository
  4. 4. Extract the downloaded package to a temporary location
  5. 5. Replace the existing SuiteCRM files with the new version files, preserving your config.php and any custom directories (custom/, data/, upload/)
  6. 6. Clear all cache directories: cache/, upload/cache/, and any opcache/ APCu caches
  7. 7. Recreate the database schema if the upgrade includes schema changes by running the repair function in the CRM admin panel (Administration > Repair > Quick Repair and Rebuild)
  8. 8. Verify the RSS Feed Dashlet functionality works correctly
Caveat Minor version upgrades typically have minimal breaking changes; however, always test in a staging environment first

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

Fix this in Suitecrm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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