CVE-2021-41596 json
SuiteCRM before 7.10.33 and 7.11.22 allows information disclosure via Directory Traversal.
published 5y ago modified 4mo ago also BIT-suitecrm-2021-41596 , EUVD-2021-28610
- cvss
- 5.3
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
SuiteCRM before 7.10.33 and 7.11.22 allows information disclosure via Directory Traversal. An attacker can partially include arbitrary files via the importFile parameter of the RefreshMapping import functionality.
Patch / fix
- bitnami suitecrm 7.10.33, 7.11.22
- salesagility suitecrm 7.10.33, 7.11.22
Is CVE-2021-41596 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.83% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:P/I:N/A:N |
| OSV | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| bitnami | suitecrm | <7.10.33 >=7.11.0, <7.11.22 |
7.10.33 7.11.22 |
Classification
- Weakness
-
- CWE-22 Improper Limitation of a Pathname to a Restricted Directory
References
-
suitecrm.com
vendor-advisory, web
-
docs.suitecrm.com
/admin/releases/7.10.x/#_7_10_33
release-notes, vendor-advisory, web
-
docs.suitecrm.com
/admin/releases/7.11.x/#_7_11_22
release-notes, vendor-advisory, web
-
github.com
/salesagility/SuiteCRM
product, third-party-advisory, web
-
github.com
/ach-ing/cves/blob/main/CVE-2021-41596.md
third-party-advisory, web
-
nvd.nist.gov
/vuln/detail/CVE-2021-41596
web
Sources
- CVE List CVE-2021-41596
- NVD CVE-2021-41596
- OSV BIT-suitecrm-2021-41596
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.