dbcve.org
SuitecrmApplication · Salesagility

CVE-2019-12600

CRITICAL · 9.8 CVSS v3.0 Published 2019-06-07
Fix available
A fix is available. Upgrade to 7.8.30 / 7.10.17 or later.
See remediation →
100/100
Remediation priority · Urgent
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 7.8.x before 7.8.30, 7.10.x before 7.10.17, and 7.11.x before 7.11.5 allows SQL Injection (issue 2 of 3).

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 allows attackers to manipulate database queries through unsanitized input. This can lead to unauthorized data access, data modification, or potential command execution on the underlying database server.

MitigationUpgrade SuiteCRM to version 7.8.30, 7.10.17, or 7.11.5 or later. If immediate patching is not possible, implement input validation and parameterized queries at identified injection points.

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.8.0, <= 7.8.5>= 7.8.6, <= 7.8.11>= 7.8.12, < 7.8.30>= 7.10.0, < 7.10.17>= 7.11.0, < 7.11.5

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
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/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. Locate SuiteCRM version file
    Check the SuiteCRM installation directory for a version file (commonly named version.php or shown in the admin panel under 'About'). The exact path varies by installation but is typically in the root directory or under include/
    Affected if You cannot locate a version file or the displayed version is not visible
  2. Identify installed SuiteCRM version
    Access the SuiteCRM administration interface and navigate to the About or System Information page to view the installed version number
    Affected if The version displayed is not visible or cannot be determined from the admin panel
  3. Compare version against affected ranges
    Check if the installed version falls within any of these vulnerable ranges: 7.8.0-7.8.5, 7.8.6-7.8.11, 7.8.12-7.8.29, 7.10.0-7.10.16, or 7.11.0-7.11.4
    Affected if The installed version is within any of these ranges: >= 7.8.0 and <= 7.8.5; >= 7.8.6 and <= 7.8.11; >= 7.8.12 and < 7.8.30; >= 7.10.0 and < 7.10.17; >= 7.11.0 and < 7.11.5
  4. Confirm SQL injection vector presence
    Review application access logs and user input handling for the affected SuiteCRM endpoints where unsanitized database queries could be executed through user-supplied input
    Affected if The application processes user input in database queries without visible input validation or parameterized query usage

Your SuiteCRM installation is affected if it is running any version between 7.8.0 and 7.8.29 (excluding 7.8.30), between 7.10.0 and 7.10.16, or between 7.11.0 and 7.11.4, and if the application accepts user input that reaches database query logic.

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.8.30 / 7.10.17 / 7.11.5 or later
Fixed in 7.8.307.10.177.11.5
Interim mitigation

Upgrade SuiteCRM to version 7.8.30, 7.10.17, or 7.11.5 or later. If immediate patching is not possible, implement input validation and parameterized queries at identified injection points.

Recommended fix High confidence

SuiteCRM 7.8.30, 7.10.17, or 7.11.5 (or later stable release)

  1. 1. Back up your SuiteCRM database and filesystem completely before proceeding
  2. 2. Download the appropriate SuiteCRM version for your branch: 7.8.30+, 7.10.17+, or 7.11.5+ (latest stable recommended)
  3. 3. Put the application in maintenance mode or restrict admin access
  4. 4. Extract the new SuiteCRM files to your web server document root, overwriting existing files
  5. 5. Run the database upgrade script: php bin/console suitecrm:app:upgrade -v <version>
  6. 6. Clear the cache: rm -rf cache/*
  7. 7. Repair and rebuild: Admin > Repair > Quick Repair and Rebuild
  8. 8. Verify the installation by logging in and testing core functionality
Caveat Review custom themes, logic hooks, and workflow definitions for compatibility with the target version; test in staging first

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
  • Testing3.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,670
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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