Synced 07 Nov 2026 15:45 UTC Account
← SuiteCRM

SuiteCRM vulnerabilities: known CVEs & security history

SalesAgility · CRM · 5 tracked CVEs · 0 actively exploited · updated November 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all SuiteCRM release lines — 5 in total. A CVE here doesn't mean your version is affected — check SuiteCRM's current status and the safe version to run.

5
known CVEs
0
actively exploited (KEV)
1
critical severity
0
ransomware-linked

Known SuiteCRM CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2022-50589 critical 9.8 1% 2025
CVE-2019-25664 high 7.1 0% 2026
CVE-2019-25663 high 7.1 0% 2026
CVE-2025-41384 medium 6.1 0% 2025
CVE-2022-50590 medium 5.3 0% 2025

Is my SuiteCRM version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your SuiteCRM version → · Monitor SuiteCRM for new CVEs →

SuiteCRM vulnerabilities — frequently asked

How many known vulnerabilities does SuiteCRM have?

IsItPatched tracks 5 CVEs for SuiteCRM. 1 is critical-severity and 2 high-severity. These span every release line — what matters is whether the version you run is affected.

Does SuiteCRM have any actively-exploited vulnerabilities?

None of SuiteCRM's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe SuiteCRM vulnerability?

Among tracked issues, CVE-2022-50589 (CRITICAL, CVSS 9.8) ranks highest — a SQL injection weakness.

Is SuiteCRM safe to use?

It depends on the version. The latest supported SuiteCRM release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: SuiteCRM security status · SuiteCRM end-of-life · actively-exploited CVEs. Always verify against SalesAgility's advisories — see our disclaimer.