dbcve.org
SuitecrmApplication · Salesagility

CVE-2024-49772

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. In SuiteCRM versions 7.14.4, poor input validation allows authenticated user do a SQL injection attack. Authenticated user with low pivilege can leak all data in database. This issue has been addressed in releases 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

SQL injection vulnerability in SuiteCRM caused by poor input validation in version 7.14.4. An authenticated user with low privileges can inject malicious SQL queries through unsanitized input fields to exfiltrate sensitive data from the database.

MitigationUpgrade SuiteCRM to version 7.14.6 or 8.7.1 (or later). No workarounds exist; immediate patching is required given the high CVSS score and data exposure risk.

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. Determine your SuiteCRM version
    Log into the SuiteCRM admin panel and navigate to Admin > System Information, or check the version.php file in the SuiteCRM root directory
    Affected if The installed version is 7.14.4, or falls below 7.14.6 in the 7.x branch, or is 8.0.0 through 8.7.0 in the 8.x branch
  2. Confirm user authentication is enabled
    Verify that the SuiteCRM application has user authentication active, as this vulnerability requires an authenticated user with low privileges
    Affected if User authentication is enabled and low-privilege user accounts exist in the system
  3. Identify accessible input modules
    Review which SuiteCRM modules allow user input, particularly custom fields or search functionality, as the injection occurs through unsanitized input fields
    Affected if Any user-accessible input fields exist in modules accessible to low-privilege users

Your environment is affected if you are running SuiteCRM version 7.14.4 or any version from 7.x below 7.14.6, or any version from 8.0.0 through 8.7.0, and you have authenticated users with access to input fields.

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). No workarounds exist; immediate patching is required given the high CVSS score and data exposure risk.

Recommended fix High confidence

SuiteCRM 7.14.6 for 7.x branch or SuiteCRM 8.7.1 for 8.x branch

  1. 1. Back up the SuiteCRM database completely before proceeding with any upgrade
  2. 2. Back up all SuiteCRM files and the entire installation directory
  3. 3. Place the application in maintenance mode or take the server offline to prevent user access during upgrade
  4. 4. For SuiteCRM 7.x installations: download version 7.14.6 from the official SuiteCRM repository
  5. 5. For SuiteCRM 8.x installations: download version 8.7.1 from the official SuiteCRM repository
  6. 6. Extract the new version files and replace the existing installation files
  7. 7. Run any database upgrade scripts included in the new version
  8. 8. Clear all cache directories (cache/, data/, upload/)
Caveat Standard upgrade risks apply - test in staging first, review release notes for any configuration or customization changes required

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
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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