dbcve.org
SuitecrmApplication

CVE-2026-33289

CRITICAL · 9.8 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 →
100/100
Remediation priority · Urgent
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, an LDAP Injection vulnerability exists in the SuiteCRM authentication flow. The application fails to properly sanitize user-supplied input before embedding it into the LDAP search filter. By injecting LDAP control characters, an unauthenticated attacker can manipulate the query logic, which can lead to authentication bypass or information disclosure. 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 versions prior to 7.15.1 and 8.9.3 contain an LDAP injection vulnerability in the authentication flow where user-supplied input is not properly sanitized before being embedded in LDAP search filters. An unauthenticated attacker can inject LDAP control characters to manipulate query logic, potentially bypassing authentication or disclosing sensitive information.

MitigationUpgrade to SuiteCRM version 7.15.1 or 8.9.3 or later. If immediate upgrade is not possible, implement proper input validation and LDAP filter escaping for all user-supplied parameters used in LDAP queries.

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 SuiteCRM version
    Locate the version file or admin panel in your SuiteCRM installation and record the exact version number
    Affected if the installed version is below 7.15.1, or is 8.0.0 through 8.9.2 inclusive
  2. Confirm LDAP authentication is in use
    Check your SuiteCRM configuration files or authentication settings to determine if LDAP authentication is enabled and configured
    Affected if LDAP authentication is not enabled - the vulnerability only applies to environments using LDAP for user authentication
  3. Review LDAP filter implementation
    Examine the LDAP query code in the authentication module for proper escaping of user-supplied input before embedding in search filters
    Affected if user-provided parameters are used directly in LDAP search filters without escaping LDAP special characters (such as * ( ) \ NUL)
  4. Compare version to affected ranges
    Document your exact SuiteCRM version and confirm it falls outside the fixed versions 7.15.1+ and 8.9.3+
    Affected if your version is below 7.15.1 or between 8.0.0 and 8.9.2 inclusive and you use LDAP authentication

You are affected if your SuiteCRM version is less than 7.15.1 or between 8.0.0 and 8.9.2 AND LDAP authentication is enabled in your environment.

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 to SuiteCRM version 7.15.1 or 8.9.3 or later. If immediate upgrade is not possible, implement proper input validation and LDAP filter escaping for all user-supplied parameters used in LDAP queries.

Recommended fix High confidence

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

  1. 1. Identify the currently installed SuiteCRM version by checking the version file or admin interface.
  2. 2. For SuiteCRM 7.x versions (< 7.15.1): Upgrade to version 7.15.1 or later.
  3. 3. For SuiteCRM 8.x versions (>= 8.0.0, < 8.9.3): Upgrade to version 8.9.3 or later.
  4. 4. Download the appropriate upgrade package from the official SuiteCRM repository (github.com/salesagility/SuiteCRM) or the official SuiteCRM website.
  5. 5. Before upgrading, perform a complete backup of the database and files.
  6. 6. Follow the standard SuiteCRM upgrade procedure: disable scheduled jobs, clear cache, run the upgrade, and verify functionality.
  7. 7. After upgrade, verify that LDAP authentication still functions correctly and test for any regressions.
Caveat Review the release notes for any specific breaking changes between your current version and the target version before upgrading

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

Fix this in Suitecrm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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