dbcve.org
SuitecrmApplication · Salesagility

CVE-2025-64493

MEDIUM · 6.5 CVSS v3.1 Published 2025-11-08
Fix available
A fix is available. Upgrade to 8.9.1 or later.
See remediation →
71/100
Remediation priority · Elevated
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 versions 8.6.0 through 8.9.0, there is an authenticated, blind (time-based) SQL-injection inside the appMetadata-operation of the GraphQL-API. This allows extraction of arbitrary data from the database, and does not require administrative access. This issue is fixed in version 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

Authenticated blind time-based SQL injection in the appMetadata GraphQL API operation of SuiteCRM versions 8.6.0 through 8.9.0 allows attackers with valid user credentials to extract arbitrary data from the database using time-based inference techniques, without requiring administrative access.

MitigationUpgrade SuiteCRM to version 8.9.1 or later to remediate this vulnerability.

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:>= 8.6.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
None
Availability
None

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

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 installation
    Locate the SuiteCRM installation directory and confirm it is Salesagility SuiteCRM rather than another CRM product.
    Affected if The product is not SuiteCRM, this CVE does not apply.
  2. Check installed SuiteCRM version
    Access the SuiteCRM admin About page or examine the version information in the installation configuration files. Compare the version number to the affected range.
    Affected if The installed version is greater than or equal to 8.6.0 AND less than 8.9.1, meaning versions 8.6.0, 8.7.x, 8.8.x, and 8.9.0 are affected.
  3. Verify GraphQL API is accessible
    Confirm that the SuiteCRM GraphQL API endpoint is accessible and appMetadata queries can be executed. This is typically at /graphql/ or similar endpoint in the web interface.
    Affected if The GraphQL API is not exposed or appMetadata operation is unavailable, the vulnerability cannot be exploited in this configuration.
  4. Confirm user authentication is possible
    Determine whether valid user credentials exist for the SuiteCRM instance, as the vulnerability requires authenticated access.
    Affected if The instance does not allow user login or has no valid user accounts, the exploitation vector is not present.

If the environment runs SuiteCRM version 8.6.0 through 8.9.0 with an accessible GraphQL API and valid user credentials exist, the environment is affected by this SQL injection vulnerability.

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 8.9.1 or later
Fixed in 8.9.1
Interim mitigation

Upgrade SuiteCRM to version 8.9.1 or later to remediate this vulnerability.

Recommended fix High confidence

8.9.1

  1. Backup the SuiteCRM database before proceeding with any upgrade
  2. Backup all custom code, themes, and configuration files in the SuiteCRM installation directory
  3. Download SuiteCRM version 8.9.1 from the official source (docs.suitecrm.com or github.com)
  4. Replace the existing SuiteCRM files with the new version 8.9.1 files
  5. Run the SuiteCRM upgrade installer or database repair/upgrade functions
  6. Clear the SuiteCRM cache (cache/ directory) to ensure the new version loads correctly
  7. Verify the upgrade was successful by logging in and testing core CRM functionality

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

Fix this in Suitecrm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing6.0 h
  • Review / QA3.0 h
18.0 hours of engineering $3,120
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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