dbcve.org
SuitecrmApplication · Salesagility

CVE-2025-64490

HIGH · 8.3 CVSS v3.1 Published 2025-11-08
Fix available
A fix is available. Upgrade to 7.14.8 / 8.9.1 or later.
See remediation →
89/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. Versions 7.14.7 and prior, 8.0.0-beta.1 through 8.9.0 allow a low-privileged user with a restrictive role to view and create work items through the Resource Calendar and project screens, even when the related modules (Projects, Project Tasks, Tasks, Leads, Accounts, Meetings, Calls) are explicitly set to Disabled/None in Role Management. This indicates inconsistent ACL/RBAC enforcement across modules and views, resulting in unauthorized data exposure and modification. This issue is fixed in versions 7.14.8 and 8.9.1.

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 7.14.7 and prior, and 8.0.0-beta.1 through 8.9.0 contain an ACL/RBAC bypass vulnerability where low-privileged users with restrictive roles can still access and modify data in Projects, Project Tasks, Tasks, Leads, Accounts, Meetings, and Calls modules through the Resource Calendar and project screens, even when these modules are explicitly set to Disabled/None in Role Management. This results in unauthorized data exposure and modification.

MitigationUpgrade SuiteCRM to version 7.14.8 or 8.9.1 or later. After upgrading, verify that role-based access controls properly enforce module restrictions for all user roles.

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.8>= 8.0.0, < 8.9.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
Low

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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 SuiteCRM version
    Check the SuiteCRM version by navigating to Admin > System Settings, or locate the version.php file in the SuiteCRM root directory (usually at ./include/portal_version.php or ./suitecrm_version.php).
    Affected if The installed version is 7.14.7 or prior, or between 8.0.0-beta.1 and 8.9.0 inclusive.
  2. Identify active modules
    Navigate to Admin > Module Builder or Admin > Display Modules and Subpanels to see which of the following modules are enabled: Projects, Project Tasks, Tasks, Leads, Accounts, Meetings, Calls.
    Affected if Any of these modules are active/enabled in the CRM.
  3. Review role configurations
    Navigate to Admin > Role Management and examine each role. For each role, check if the affected modules (Projects, Project Tasks, Tasks, Leads, Accounts, Meetings, Calls) are explicitly set to Disabled or have access set to None/Restricted.
    Affected if There exist roles where these modules are set to Disabled/None but the roles are assigned to users.
  4. Test access with low-privilege accounts
    Log in with a user account assigned a restrictive role (where affected modules are set to Disabled/None). Attempt to access the Resource Calendar (typically at index.php?module=ResourceCalendar) and project-related screens (index.php?module=Project).
    Affected if The user can view or modify data in Projects, Project Tasks, Tasks, Leads, Accounts, Meetings, or Calls despite the module being set to Disabled/None in their role.

You are affected if your SuiteCRM version is below 7.14.8 or below 8.9.1, and you have users with restrictive roles that can still access the vulnerable modules via Resource Calendar or project screens.

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.8 / 8.9.1 or later
Fixed in 7.14.88.9.1
Interim mitigation

Upgrade SuiteCRM to version 7.14.8 or 8.9.1 or later. After upgrading, verify that role-based access controls properly enforce module restrictions for all user roles.

Recommended fix High confidence

Upgrade to SuiteCRM 7.14.8 (for 7.x installations) or SuiteCRM 8.9.1 (for 8.x installations)

  1. 1. Create a complete backup of the SuiteCRM database and all application files including config.php
  2. 2. Put the SuiteCRM instance into maintenance mode or notify users of scheduled downtime
  3. 3. Download the appropriate fixed version package (7.14.8 for 7.x branch or 8.9.1 for 8.x branch) from the official SuiteCRM repository or download page
  4. 4. If upgrading from 7.x to 7.14.8: Extract the new version over the existing installation, preserving the config.php and any custom entry points
  5. 5. If upgrading from 8.x to 8.9.1: Extract the new version and run any provided upgrade scripts from the command line
  6. 6. Clear all cached files by deleting the cache/ directory contents (except .htaccess)
  7. 7. Repair and rebuild the database using Admin > Repair > Quick Repair and Rebuild in the UI, or via CLI: php bin/console suitecrm:app:repair
  8. 8. Verify that Role Management settings are now properly enforced by testing with a low-privileged user account that has restricted roles
Caveat Review the official upgrade notes for your version path; major branch upgrades (e.g., 7.x to 8.x) may require schema or customization adjustments

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
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
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,808.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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