CVE-2023-3627 json
Cross-Site Request Forgery (CSRF) in salesagility/suitecrm-core
published 2023-07-11 3 y ago modified 2026-06-17 4 mo ago also BIT-suitecrm-2023-3627 , EUVD-2023-44275
- cvss
- 8.1
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 28%
- public exploits
- 0
- none known
Summary
Cross-Site Request Forgery (CSRF) in GitHub repository salesagility/suitecrm-core prior to 8.3.1.
Patch / fix
- bitnami suitecrm 8.3.1
- salesagility salesagility/suitecrm-core 8.3.1
- salesagility suitecrm 8.3.1
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
0.35% chance of exploitation in the next 30 days, higher than 28% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/558b3dce-db03-47ba-b60b-c6eb578e04f1 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 8.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N |
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
| OSV | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | suitecrm | <8.3.1 |
8.3.1 |
Affected products
- salesagility salesagility/suitecrm-core
- salesagility suitecrm
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/salesagility/suitecrm-core/commit/78285702d76317f081b1fbc59cb2754e93b9a4c3
patch, web
-
huntr.dev
/bounties/558b3dce-db03-47ba-b60b-c6eb578e04f1
exploit, issue-tracking, patch, third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2023-3627
web
Sources
- CVE List CVE-2023-3627
- NVD CVE-2023-3627
- OSV BIT-suitecrm-2023-3627
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.