dbcve.org
SuitecrmApplication · Salesagility

CVE-2024-49774

HIGH · 7.2 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 →
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. SuiteCRM relies on the blacklist of functions/methods to prevent installation of malicious MLPs. But this checks can be bypassed with some syntax constructions. SuiteCRM uses token_get_all to parse PHP scripts and check the resulted AST against blacklists. But it doesn't take into account all scenarios. 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 · moderate confidence

SuiteCRM uses PHP's token_get_all function to parse PHP scripts and validates the resulting AST against a blacklist to prevent installation of malicious MLP (Module/Plugin/Package) extensions. However, the blacklist validation can be bypassed using certain PHP syntax constructions that aren't properly handled by the AST checking logic, allowing execution of restricted functions despite the blacklist.

MitigationUpgrade to SuiteCRM version 7.14.6 or 8.7.1. No workarounds are available; the blacklist validation logic must be patched.

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
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 in your SuiteCRM installation (typically in the root directory as version.php or in the about page of the admin interface). Open the file and read the $suitecrm_version variable.
    Affected if The installed version is less than 7.14.6 OR greater than or equal to 8.0.0 but less than 8.7.1
  2. Verify MLP extension upload capability
    Log into the SuiteCRM admin panel and navigate to the Module Loader section (Admin > Module Loader). Check if the interface allows uploading MLP/zip packages for installation.
    Affected if The Module Loader is accessible and allows uploading packages, indicating the vulnerable feature is enabled
  3. Check PHP token handling configuration
    Review your PHP configuration (php.ini) for any settings that affect token parsing behavior. Confirm PHP version by running 'php -v' or viewing phpinfo().
    Affected if PHP is configured to process tokens normally (default behavior); the bypass affects how token_get_all parses certain syntax constructions

You are affected if your SuiteCRM version falls below 7.14.6 or between 8.0.0 and 8.7.1 (exclusive), and the Module Loader feature is accessible in your installation.

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 to SuiteCRM version 7.14.6 or 8.7.1. No workarounds are available; the blacklist validation logic must be patched.

Recommended fix High confidence

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

  1. 1. Determine which major version line of SuiteCRM is currently installed (7.x or 8.x)
  2. 2. For SuiteCRM 7.x versions: Upgrade to version 7.14.6
  3. 3. For SuiteCRM 8.x versions (>= 8.0.0): Upgrade to version 8.7.1
  4. 4. After upgrade, verify the installation is working correctly
  5. 5. Test that MLP (Module Loadable Package) functionality still works as expected

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
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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