dbcve.org
SuitecrmApplication

CVE-2026-29109

HIGH · 7.2 CVSS v3.1 Published 2026-03-20
Fix available
A fix is available. Upgrade to 8.9.3 or later.
See remediation →
78/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. Versions up to and including 8.9.2 contain an unsafe deserialization vulnerability in the SavedSearch filter processing component that allows an authenticated administrator to execute arbitrary system commands on the server. `FilterDefinitionProvider.php` calls `unserialize()` on user-controlled data from the `saved_search.contents` database column without restricting instantiable classes. Version 8.9.3 patches 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 versions 8.9.2 and below contain an unsafe deserialization vulnerability in FilterDefinitionProvider.php. The application calls unserialize() on data from the saved_search.contents database column without restricting allowed classes, allowing an authenticated administrator to inject malicious PHP objects that execute arbitrary system commands.

MitigationUpgrade to SuiteCRM 8.9.3 or later to receive the patched version. If immediate upgrading is not feasible, restrict administrator account access and audit the saved_search table for suspicious serialized content.

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

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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. Identify installed SuiteCRM version
    Locate the version file or admin panel version display in your SuiteCRM installation. Common locations include config.php, a version.php file in the root directory, or the About section in the admin interface.
    Affected if The installed version is 8.9.2 or below (any version prior to 8.9.3)
  2. Confirm FilterDefinitionProvider.php is present
    Locate the FilterDefinitionProvider.php file within the SuiteCRM source code directory structure, typically under src/Security/Validation/filters/ or similar paths depending on your installation layout.
    Affected if The file exists in the application and contains an unserialize() call on user-controlled data
  3. Verify saved_search table exists and contains data
    Access the SuiteCRM database and query the saved_search table. Check the structure for a contents or related column that stores serialized search definitions.
    Affected if The saved_search table exists and contains records with serialized data in the contents or similar column
  4. Confirm administrator account access exists
    Review user accounts in SuiteCRM to determine if any administrator-level accounts are present. This vulnerability requires an authenticated administrator to exploit.
    Affected if There is at least one active administrator account in the system that could be used to inject malicious serialized objects
  5. Inspect saved_search contents for anomalies
    Query the database directly to examine the saved_search.contents column for unexpected serialized patterns or objects that do not match expected search filter structures.
    Affected if Any record in saved_search contains serialized data with unexpected PHP object types or patterns not consistent with normal saved search functionality

You are affected if your SuiteCRM installation is version 8.9.2 or below, the FilterDefinitionProvider.php file uses unserialize() on saved_search data without class restrictions, and an authenticated administrator account exists in the system.

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 8.9.3 or later
Fixed in 8.9.3
Interim mitigation

Upgrade to SuiteCRM 8.9.3 or later to receive the patched version. If immediate upgrading is not feasible, restrict administrator account access and audit the saved_search table for suspicious serialized content.

Recommended fix High confidence

8.9.3

  1. Backup your SuiteCRM installation and database before proceeding
  2. Download SuiteCRM version 8.9.3 from the official SuiteCRM website or repository
  3. Extract the new version files to your server, overwriting the existing installation
  4. Run the upgrade repair and rebuild scripts via the SuiteCRM admin interface or command line
  5. Verify that the application is functioning correctly after the upgrade

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

Fix this in Suitecrm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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