CVE-2019-17310
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 Campaigns module by an Admin 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 Campaigns module. An authenticated user with Admin privileges can inject and execute arbitrary PHP code due to insufficient input validation when processing Campaign module data.
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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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.
-
Determine installed SugarCRM versionLocate the version file in the SugarCRM installation directory (typically includes a version.php or similar file in the root or include directory). Open it and read the version number.Affected if The installed version falls within any of these ranges: 7.9.0.0 to 7.9.5.0, 8.0.0 to 8.0.4, or 9.0.0 to 9.0.2.
-
Verify Campaigns module is enabledLog into the SugarCRM application as an administrator. Navigate to Admin > Module Loader or check the module list to confirm the Campaigns module is installed and active.Affected if The Campaigns module is present and enabled in the SugarCRM instance.
-
Confirm admin-level access existsLog into SugarCRM and check your user profile or Admin > User Management to verify your account has Administrator privileges.Affected if An authenticated user with Admin-level access can log into the system.
-
Identify vulnerable Campaign data entry pointNavigate to the Campaigns module in the SugarCRM UI. Examine how campaign data (such as campaign names, tracking parameters, or template fields) is processed and submitted. Look for input fields that accept arbitrary text.Affected if The Campaigns module accepts user input in fields that are not properly sanitized before PHP execution.
A user is affected if they run SugarCRM version 7.9.0.0-7.9.5.0, 8.0.0-8.0.4, or 9.0.0-9.0.2 with the Campaigns module enabled and have admin accounts that could be compromised.
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 to remediate this vulnerability. After upgrading, verify the Campaigns module functions correctly and the code injection vector is neutralized.
- Consultation4.0 h
- Implementation6.0 h
- Testing5.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 $5,072.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17310 — 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-17310 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