dbcve.org
SuitecrmApplication · Salesagility

CVE-2021-25960

HIGH · 8.0 CVSS v3.1 Published 2021-09-29
Fix available
A fix is available. Upgrade to 7.10.32 / 7.11.21 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable Patch available

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
In “SuiteCRM” application, v7.11.18 through v7.11.19 and v7.10.29 through v7.10.31 are affected by “CSV Injection” vulnerability (Formula Injection). A low privileged attacker can use accounts module to inject payloads in the input fields. When an administrator access accounts module to export the data as a CSV file and opens it, the payload gets executed. This was not fixed properly as part of CVE-2020-15301, allowing the attacker to bypass the security measure.

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

A detailed technical summary for this CVE is being prepared.

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.10.29, < 7.10.32>= 7.11.18, < 7.11.21

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H

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.

dbcve · scoped
Upgrade available Upgrade to 7.10.32 / 7.11.21 or later
Fixed in 7.10.327.11.21
Vendor patch github.com →
Recommended fix High confidence

SuiteCRM 7.10.32 or SuiteCRM 7.11.21

  1. 1. Backup your SuiteCRM instance and database before performing any upgrade
  2. 2. Verify your current SuiteCRM version in Admin > System Information
  3. 3. Download SuiteCRM 7.10.32 (if on 7.10.x branch) or SuiteCRM 7.11.21 (if on 7.11.x branch) from the official repository at https://github.com/salesagility/SuiteCRM/releases
  4. 4. Upload the new version files to your server, replacing the existing installation
  5. 5. Run the repair and rebuild functions via Admin > Repair > Quick Repair and Rebuild
  6. 6. Clear the cache by deleting files in cache/ directory
  7. 7. Verify the upgrade was successful and test the CSV export functionality in the Accounts module to confirm the vulnerability is mitigated
Caveat Review release notes for any configuration or customization changes between your current version and the target version before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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