CVE-2019-17303
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 · uneditedSugarCRM before 8.0.4 and 9.x before 9.0.2 allows PHP code injection in the MergeRecords module by a Developer 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 confidenceSugarCRM before versions 8.0.4 and 9.0.2 contains a PHP code injection vulnerability in the MergeRecords module that allows authenticated Developer-level users to inject and execute arbitrary PHP code on the server, potentially leading to full system compromise.
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>= 7.9.0.0, < 7.9.5.0>= 8.0.0, < 8.0.4>= 9.0.0, < 9.0.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify SugarCRM versionLocate the SugarCRM version number in the admin panel under 'About SugarCRM' or check the version.php file in the installation directoryAffected if The installed version falls within >= 7.9.0.0 and < 7.9.5.0, OR >= 8.0.0 and < 8.0.4, OR >= 9.0.0 and < 9.0.2
-
Verify user permission levelCheck the role assignments for users in the SugarCRM admin panel under 'Users' and 'Roles'. Look for accounts assigned the Developer role or elevated permissionsAffected if Any user account with Developer-level or higher permissions exists in the system
-
Confirm MergeRecords module accessibilityNavigate to the MergeRecords module in the SugarCRM interface or check the module loader to see if MergeRecords is enabled and accessibleAffected if The MergeRecords module is enabled and available to users in the system
-
Review MergeRecords activity logsCheck SugarCRM audit logs and server access logs for unusual or suspicious MergeRecords operations, particularly requests with unexpected parametersAffected if Audit logs show MergeRecords usage with unusual parameter patterns or requests originating from Developer-level accounts that are unexpected
Your environment is likely affected if SugarCRM version is below 8.0.4 or 9.0.2 AND a user with Developer-level permissions can access the MergeRecords module.
Generated from the published advisory. Verify against your own configuration.
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 data7.9.5.08.0.49.0.2
Upgrade SugarCRM to version 8.0.4 or later, or 9.0.2 or later. Until patched, restrict Developer-level permissions to trusted personnel only and monitor for suspicious activity in the MergeRecords module.
- Consultation3.0 h
- Implementation6.0 h
- Testing12.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,432.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17303 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-17303 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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