CVE-2020-36388 json
In CiviCRM before 5.21.3 and 5.22.x through 5.24.x before 5.24.3, users may be able to upload and execute a crafted PHAR archive.
published 5y ago modified 4mo ago also BIT-civicrm-2020-36388 , EUVD-2020-23919
- cvss
- 8.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.4%
- EPSS 1.4% chance of exploitation in 30 days, percentile 73%
- public exploits
- 0
- none known
Summary
In CiviCRM before 5.21.3 and 5.22.x through 5.24.x before 5.24.3, users may be able to upload and execute a crafted PHAR archive.
Patch / fix
- bitnami civicrm 5.21.3, 5.24.3
- civicrm civicrm 5.21.3, 5.24.3
- civicrm Debian 11 5.24.5+dfsg1-1
debian advisories DEBIAN-CVE-2020-36388
Is CVE-2020-36388 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.44% chance of exploitation in the next 30 days, higher than 73% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- blog.sonarsource.com https://blog.sonarsource.com/civicrm-code-execution-vulnerability-chain-explained/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
| NVD | 2.0 | 6.5 | AV:N/AC:L/Au:S/C:P/I:P/A:P |
| OSV | 3.1 | 8.8 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | civicrm | <5.21.3 >=5.22.0, <5.24.3 |
5.21.3 5.24.3 |
Classification
- Weakness
-
- CWE-434 Unrestricted Upload of File with Dangerous Type
References
-
blog.sonarsource.com
/civicrm-code-execution-vulnerability-chain-explained/
exploit, third-party-advisory, web
-
civicrm.org
/advisory/civi-sa-2020-03
vendor-advisory, web
Sources
- CVE List CVE-2020-36388
- NVD CVE-2020-36388
- OSV BIT-civicrm-2020-36388
Fencer Intel 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.