dbcve.org
SuitecrmApplication · Salesagility

CVE-2024-50332

HIGH · 8.8 CVSS v3.1 Published 2024-11-05
Fix available
A fix is available. Upgrade to 7.14.6 / 8.7.1 or later.
See remediation →
94/100
Remediation priority · Urgent
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. Insufficient input value validation causes Blind SQL injection in DeleteRelationShip. This issue has been addressed in versions 7.14.6 and 8.7.1. Users are advised to upgrade. There are no known workarounds for this vulnerability.

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.14.6 and 8.7.1 contain a blind SQL injection vulnerability in the DeleteRelationShip function due to insufficient input validation. An attacker with access to the CRM can inject malicious SQL queries through unvalidated input parameters, potentially exfiltrating sensitive data from the database.

MitigationUpgrade SuiteCRM to version 7.14.6 or 8.7.1 or later. Since no workarounds exist, immediate patching is required to remediate this high-severity SQL injection 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.14.6>= 8.0.0, < 8.7.1

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
High

CVSS:3.1/AV:N/AC:L/PR:L/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 installed
    Locate the version file in the SuiteCRM installation directory. For v7, check include/VCargo.php or the admin panel under 'About'. For v8, check the version.json file or admin panel.
    Affected if The installed version is below 7.14.6, or is 8.0.0 through 8.7.0
  2. Confirm DeleteRelationShip function exists
    Search the codebase for the DeleteRelationShip function definition. In v7, look in modules/*/DeleteRelationship.php or similar. In v8, check the API endpoint handling relationship deletion.
    Affected if The function exists in the installation, indicating the vulnerable code path is present
  3. Verify CRM user access level
    The vulnerability requires an attacker to have access to the CRM. Check which user roles have access to relationship deletion features in the CRM UI or API.
    Affected if Authenticated users with access to relationship management features can reach the vulnerable function
  4. Review input validation in DeleteRelationShip
    Examine the source code of the DeleteRelationShip function to determine if input parameters are validated, sanitized, or use parameterized queries. Look for direct use of user input in SQL statements.
    Affected if Parameters passed to SQL queries are not properly sanitized or bound

The environment is affected if SuiteCRM version is below 7.14.6 or between 8.0.0 and 8.7.0, and the DeleteRelationShip function lacks proper input validation for SQL injection.

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.14.6 / 8.7.1 or later
Fixed in 7.14.68.7.1
Interim mitigation

Upgrade SuiteCRM to version 7.14.6 or 8.7.1 or later. Since no workarounds exist, immediate patching is required to remediate this high-severity SQL injection vulnerability.

Recommended fix High confidence

7.14.6 for 7.x line, 8.7.1 for 8.x line

  1. Backup your SuiteCRM installation and database before proceeding with any upgrade
  2. Determine your current major version (7.x or 8.x) to select the appropriate upgrade path
  3. For SuiteCRM 7.x users: Download version 7.14.6 from the official SuiteCRM repository
  4. For SuiteCRM 8.x users: Download version 8.7.1 from the official SuiteCRM repository
  5. Follow the official SuiteCRM upgrade documentation to apply the update
  6. Verify the upgrade was successful by logging in and checking the SuiteCRM version information

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

Fix this in Suitecrm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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