dbcve.org
SugarcrmApplication

CVE-2019-17297

HIGH · 8.8 CVSS v3.1 Published 2019-10-07
Fix available
A fix is available. Upgrade to 7.9.5.0 / 8.0.4 or later.
See remediation →
94/100
Remediation priority · Urgent
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
SugarCRM before 8.0.4 and 9.x before 9.0.2 allows SQL injection in the Quotes module by a Regular user.

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 SugarCRM's Quotes module allows authenticated Regular users to inject arbitrary SQL queries through unsanitized input, potentially enabling data exfiltration or database compromise.

MitigationUpgrade SugarCRM to version 8.0.4 or later (8.x branch) or 9.0.2 or later (9.x branch) to patch the SQL injection vulnerability in the Quotes module.

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
SugarcrmApplication
Affected:>= 7.9.0.0, < 7.9.5.0>= 8.0.0, < 8.0.4>= 9.0.0, < 9.0.2

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
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify installed SugarCRM version
    Locate the version file (sugar_version.json in the SugarCRM root directory) or access the Admin > About page in the SugarCRM UI
    Affected if The installed version is 7.9.0.0 through 7.9.4.x, 8.0.0 through 8.0.3.x, or 9.0.0 through 9.0.1.x
  2. Confirm the Quotes module is enabled
    Navigate to Admin > Module Loader or Admin > Studio to verify the Quotes module is installed and active
    Affected if The Quotes module is present and enabled in the SugarCRM instance
  3. Verify user role access to Quotes
    Check Admin > Role Management to confirm Regular users have access to the Quotes module
    Affected if Regular or low-privilege users have Create/Edit/Read access to the Quotes module
  4. Identify web server and endpoint exposure
    Review the SugarCRM web root for the Quotes module controller (typically in src/Modules/Quotes or similar path)
    Affected if The Quotes module endpoint is accessible over HTTP/HTTPS to authenticated users

A user is affected if their SugarCRM version falls within 7.9.0.0-7.9.4.x, 8.0.0-8.0.3.x, or 9.0.0-9.0.1.x AND the Quotes module is enabled with access granted to regular users.

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.

From vendor data
Upgrade available Upgrade to 7.9.5.0 / 8.0.4 / 9.0.2 or later
Fixed in 7.9.5.08.0.49.0.2
Interim mitigation

Upgrade SugarCRM to version 8.0.4 or later (8.x branch) or 9.0.2 or later (9.x branch) to patch the SQL injection vulnerability in the Quotes module.

Fix this in Sugarcrm Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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