dbcve.org
SuitecrmApplication · Salesagility

CVE-2024-36407

MEDIUM · 6.5 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 →
74/100
Remediation priority · Elevated
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 Customer Relationship Management (CRM) software application. In versions prior to 7.14.4 and 8.6.1, a user password can be reset from an unauthenticated attacker. The attacker does not get access to the new password. But this can be annoying for the user. This attack is also dependent on some password reset functionalities being enabled. It also requires the system using php 7, which is not an officially supported version. 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

SuiteCRM versions prior to 7.14.4 and 8.6.1 contain an unauthenticated password reset vulnerability that allows remote attackers to trigger password resets for legitimate users. The attack does not expose the new password to the attacker, making it primarily an annoyance or denial-of-service style attack rather than account takeover. Successful exploitation requires password reset functionality to be enabled and the system to be running PHP 7.

MitigationUpgrade SuiteCRM to version 7.14.4 or 8.6.1 or later. Additionally, disable password reset functionality if not required and migrate from the unsupported PHP 7 to a supported PHP version.

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
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:L

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 the SuiteCRM installation directory (typically version.php or a similar version indicator file in the root or include directory) and read the version number
    Affected if version is less than 7.14.4 or greater than or equal to 8.0.0 but less than 8.6.1
  2. Verify PHP runtime version
    Run 'php -v' from command line or call phpinfo() via a test script to determine the PHP version powering the web server
    Affected if PHP version is 7.x (any minor version)
  3. Confirm password reset functionality status
    Access SuiteCRM admin settings (System > Password Management or similar) or inspect the configuration file (config.php) for the password_reset setting
    Affected if password reset functionality is enabled (value is set to true or 1)

You are affected if your SuiteCRM version is in the vulnerable range AND password reset is enabled AND the system runs PHP 7, as all three conditions are required for successful exploitation.

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. Additionally, disable password reset functionality if not required and migrate from the unsupported PHP 7 to a supported PHP version.

Recommended fix High confidence

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

  1. Determine the currently installed SuiteCRM version (check version.php or admin panel)
  2. If running SuiteCRM 7.x: upgrade to version 7.14.4 or later
  3. If running SuiteCRM 8.x: upgrade to version 8.6.1 or later
  4. After upgrading, verify the password reset functionality works correctly
  5. Ensure PHP is upgraded from version 7 to a supported PHP 8.x version, as PHP 7 is no longer officially supported
Caveat Upgrading from SuiteCRM 7.x to 8.x may introduce breaking changes; review the migration documentation before upgrading across major versions

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

Fix this in Suitecrm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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