dbcve.org
SuitecrmApplication · Salesagility

CVE-2020-15301

HIGH · 7.8 CVSS v3.1 Published 2020-11-18
Fix available
A fix is available. Upgrade to after 7.11.13 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 through 7.11.13 allows CSV Injection via registration fields in the Accounts, Contacts, Opportunities, and Leads modules. These fields are mishandled during a Download Import File Template operation.

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

SuiteCRM through 7.11.13 contains a CSV Injection vulnerability where registration fields in Accounts, Contacts, Opportunities, and Leads modules are not properly sanitized when generating import template files. This allows attackers to inject spreadsheet formula commands (starting with =, +, -, @) that will execute when the CSV is opened in spreadsheet software, potentially leading to arbitrary code execution.

MitigationUpgrade to SuiteCRM 7.11.14 or later which contains the patch, or implement output encoding/sanitization for formula injection characters (=, +, -, @, tab) in registration fields before CSV export.

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.11.13

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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 SuiteCRM version
    Check the installed SuiteCRM version by accessing the Admin panel (usually at /admin or /index.php?module=Administration) and navigating to 'About', or by examining the suitecrm_version.php file in the root directory. Alternatively, check the 'Admin > Diagnostics' section for version information.
    Affected if The installed version is 7.11.13 or any earlier version (e.g., 7.11.0, 7.10.x, 7.9.x). The vulnerability affects all versions up to and including 7.11.13.
  2. Confirm access to CSV import template generation
    Navigate to the Import feature in SuiteCRM. Go to the Actions menu for one of the affected modules (Accounts, Contacts, Opportunities, or Leads) and locate the 'Import' option. Verify whether an import template file can be generated or downloaded from the system.
    Affected if The CSV import template generation feature is available and accessible to users in the environment.
  3. Identify affected modules presence
    Check if the core modules Accounts, Contacts, Opportunities, and Leads are installed and active in your SuiteCRM instance. These can be verified in Admin > Module Builder or by accessing the navigation menu to see if these modules are listed.
    Affected if One or more of these modules (Accounts, Contacts, Opportunities, Leads) are present and enabled in the CRM system.
  4. Verify CSV export capability exists
    Test or inspect whether the system can export or generate CSV files from the import templates. Check the /include/Import/ directory for import related files, or look for CSV-related functions in the module loaders.
    Affected if CSV file generation capability exists for the import functionality within the affected modules.

You are affected if your SuiteCRM installation version is 7.11.13 or any earlier version (less than 7.11.14), the CSV import template feature is accessible, and the Accounts, Contacts, Opportunities, or Leads modules are present and active.

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 a release after 7.11.13
Interim mitigation

Upgrade to SuiteCRM 7.11.14 or later which contains the patch, or implement output encoding/sanitization for formula injection characters (=, +, -, @, tab) in registration fields before CSV export.

Fix this in Suitecrm Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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