CVE-2023-5350 json
SQL Injection in salesagility/suitecrm
published 2023-10-03 3 y ago modified 2026-06-17 4 mo ago also BIT-suitecrm-2023-5350 , EUVD-2023-57666
- cvss
- 6.4
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.2%
- EPSS 2.2% chance of exploitation in 30 days, percentile 82%
- public exploits
- 1
- Metasploit
Summary
SQL Injection in GitHub repository salesagility/suitecrm prior to 7.14.1.
Patch / fix
- bitnami suitecrm 7.14.1
- salesagility salesagility/suitecrm 7.14.1
Timeline
- First public exploit (Metasploit auxiliary/gather/suite_crm_export_sqli)
- Published
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2 y ago
Exploit prediction
2.17% chance of exploitation in the next 30 days, higher than 82% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Metasploit auxiliary/gather/suite_crm_export_sqli SuiteCRM authenticated SQL injection in export functionality metasploit auxiliary, normal rank, 2022-05-24
- huntr.dev https://huntr.dev/bounties/c56563cb-b74e-4174-a09a-cd07689d6736 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.4 | CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
| OSV | 3.1 | 9.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | suitecrm | <7.14.1 |
7.14.1 |
Affected products
- salesagility salesagility/suitecrm
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/salesagility/suitecrm/commit/c43eaa311fb010b7928983e6afc6f9075c3996aa
patch, web
-
huntr.dev
/bounties/c56563cb-b74e-4174-a09a-cd07689d6736
exploit, patch, third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2023-5350
web
Sources
- CVE List CVE-2023-5350
- NVD CVE-2023-5350
- OSV BIT-suitecrm-2023-5350
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.