dbcve.org
SuitecrmApplication · Salesagility

CVE-2019-12601

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 3 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 versions 7.8.x before 7.8.30, 7.10.x before 7.10.17, and 7.11.x before 7.11.5 allows remote attackers to inject malicious SQL queries through unsanitized input parameters, potentially gaining unauthorized database access, exfiltrating sensitive data, or modifying database contents.

MitigationUpgrade SuiteCRM to version 7.8.30, 7.10.17, 7.11.5 or later. If immediate patching is not possible, implement web application firewall (WAF) rules to filter malicious SQL payloads and restrict database user privileges to minimum required operations.

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 file `suitecrm_version.php` in the SuiteCRM root directory, or access the SuiteCRM About page (usually at `/index.php?action=About` or `/#about`)
    Affected if The version displayed is below 7.8.30, between 7.8.6-7.8.11, or below 7.10.17 (for 7.10.x), or below 7.11.5 (for 7.11.x)
  2. Identify exact SuiteCRM release
    Open `suitecrm_version.php` and read the `$suitecrm_version` variable, or check the version shown in the admin panel under `System > About`
    Affected if The version number matches any of the 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
  3. Verify input handling on user-facing forms
    Review application logs or HTTP traffic for unusual SQL syntax in GET/POST parameters sent to SuiteCRM endpoints, particularly search fields or filters
    Affected if Application logs show SQL error messages or unexpected database queries triggered by user input parameters
  4. Check database user privileges
    Review the database credentials used in SuiteCRM config (`dbconfig.php` or `config.php`) and verify the associated database user has only minimal privileges
    Affected if The SuiteCRM database user has elevated privileges (such as DROP, CREATE, or administrative rights) beyond SELECT, INSERT, UPDATE, DELETE

You are affected if your SuiteCRM installation version falls within 7.8.0-7.8.29, 7.10.0-7.10.16, or 7.11.0-7.11.4 and the application accepts unsanitized user input on web forms.

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, 7.11.5 or later. If immediate patching is not possible, implement web application firewall (WAF) rules to filter malicious SQL payloads and restrict database user privileges to minimum required operations.

Recommended fix High confidence

Upgrade to SuiteCRM 7.8.30, 7.10.17, or 7.11.5 (or later stable releases)

  1. 1. Back up the entire SuiteCRM database and file system before proceeding
  2. 2. Put the SuiteCRM instance into maintenance mode or inform users of planned downtime
  3. 3. Download the appropriate fixed version (7.8.30, 7.10.17, or 7.11.5) from the official SuiteCRM download page
  4. 4. Extract the new version files to a temporary directory
  5. 5. Copy the new files over the existing installation, preserving custom configurations in config.php and any custom modules in the custom/ directory
  6. 6. Run the upgrade wizard or repair/rebuild functions via Admin > Repair > Quick Repair and Rebuild
  7. 7. Clear the cache by deleting files in cache/ directory (except .gitkeep)
  8. 8. Verify the installation by logging in and testing core functionality
Caveat Standard upgrade precautions apply - test in staging first, review release notes for any breaking changes between your version and target version

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 / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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