dbcve.org
SuitecrmApplication · Salesagility

CVE-2024-36411

HIGH · 8.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 7.14.4 / 8.6.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 Customer Relationship Management (CRM) software application. In versions prior to 7.14.4 and 8.6.1, poor input validation allows for SQL Injection in EmailUIAjax displayView controller. Versions 7.14.4 and 8.6.1 contain a fix for this 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

SQL Injection vulnerability in SuiteCRM's EmailUIAjax displayView controller due to poor input validation. The vulnerability affects versions prior to 7.14.4 and 8.6.1, allowing attackers to inject malicious SQL queries through unsanitized user input in the email UI component.

MitigationUpgrade SuiteCRM to version 7.14.4 or 8.6.1 or later to apply the input validation fix. Prior to upgrade, consider restricting access to the EmailUIAjax endpoint as a temporary mitigation.

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.4>= 8.0.0, < 8.6.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
    Locate the SuiteCRM version file (typically version.php in the root directory) or check the admin panel for the installed version number
    Affected if The installed version is below 7.14.4 or is 8.0.0 through 8.6.0
  2. Confirm EmailUIAjax controller is present
    Check for the existence of the EmailUIAjax controller file in the codebase (search for EmailUIAjax in the modules/Emails directory)
    Affected if The EmailUIAjax controller exists in the installation and the version is vulnerable as identified in step 1
  3. Verify displayView action is accessible
    Review the EmailUIAjax controller to confirm the displayView method is defined and accessible, typically through web requests to the endpoint
    Affected if The displayView method is exposed and reachable without additional authentication restrictions beyond standard login

You are affected if your SuiteCRM installation is version 7.x below 7.14.4 or version 8.x between 8.0.0 and 8.6.0, and the EmailUIAjax controller with its displayView action is accessible to potential attackers.

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.4 / 8.6.1 or later
Fixed in 7.14.48.6.1
Interim mitigation

Upgrade SuiteCRM to version 7.14.4 or 8.6.1 or later to apply the input validation fix. Prior to upgrade, consider restricting access to the EmailUIAjax endpoint as a temporary mitigation.

Recommended fix High confidence

SuiteCRM 7.14.4 (for 7.x users) or SuiteCRM 8.6.1 (for 8.x users)

  1. 1. Back up your SuiteCRM database (export all tables using mysqldump or phpMyAdmin)
  2. 2. Back up all SuiteCRM files and directories, especially config.php, custom/ folder, and upload/ folder
  3. 3. Download SuiteCRM version 7.14.4 (if on 7.x branch) or 8.6.1 (if on 8.x branch) from the official SuiteCRM GitHub releases page
  4. 4. Place your instance in maintenance mode or inform users of scheduled downtime
  5. 5. For 7.x: Run the SuiteCRM upgrade wizard via admin panel > Upgrade Wizard, or manually replace core files while preserving config.php and custom directory
  6. 6. For 8.x: Replace core application files, preserving config.php, custom/, and upload/ directories
  7. 7. After file replacement, run the Repair and Rebuild functions via Admin > Repair > Quick Repair and Rebuild
  8. 8. Clear the cache by deleting all files in cache/ folder (except index.html)
Caveat Review the release notes for 7.14.4 and 8.6.1 for any breaking changes; major version upgrades (7.x to 8.x) may require additional migration steps and compatibility checks with custom modules

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

Fix this in Suitecrm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation4.0 h
  • Testing8.0 h
  • Review / QA4.0 h
20.0 hours of engineering $3,440
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,504.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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