dbcve.org
SugarcrmApplication

CVE-2019-17293

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 pmse_Project 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 the pmse_Project module of SugarCRM allows authenticated regular users to execute arbitrary SQL queries via unsanitized input, affecting versions before 8.0.4 and 9.x before 9.0.2.

MitigationUpgrade SugarCRM to version 8.0.4, 9.0.2, or later to obtain the vendor patch. Alternatively, apply vendor-supplied security patches for 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
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. Determine installed SugarCRM version
    Navigate to Admin > System Settings or check the SugarCRM version file (usually version.php in the root directory) to identify the exact version number
    Affected if The installed version falls within 7.9.0.0 to 7.9.4.x, 8.0.0 to 8.0.3, or 9.0.0 to 9.0.1
  2. Verify pmse_Project module presence
    Check if the pmse_Project module is listed and enabled in SugarCRM by navigating to Admin > Module Loader or examining the modules/pmse_Project directory in the installation
    Affected if The pmse_Project module exists and is enabled in the SugarCRM instance
  3. Confirm user authentication context
    Identify whether the user account being tested has standard (non-admin) authenticated access to the SugarCRM system
    Affected if The vulnerability can be exploited by any authenticated user with access to the pmse_Project module, not just administrators

A user is affected if their SugarCRM installation version is 7.9.x before 7.9.5.0, 8.0.x before 8.0.4, or 9.0.x before 9.0.2, AND the pmse_Project module is installed and accessible to authenticated 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, 9.0.2, or later to obtain the vendor patch. Alternatively, apply vendor-supplied security patches for this vulnerability.

Fix this in Sugarcrm Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
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,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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