CVE-2021-39198 json
The disqualify lead action may be executed without CSRF token check
published 4y ago modified 4mo ago also GHSA-vf7h-6246-hm43 , EUVD-2021-2396
- cvss
- 4.2
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
OroCRM is an open source Client Relationship Management (CRM) application. Affected versions we found to suffer from a vulnerability which could an attacker is able to disqualify any Lead with a Cross-Site Request Forgery (CSRF) attack. There are no workarounds that address this vulnerability and all users are advised to update their package.
Patch / fix
- packagist oro/crm 4.1.17, 4.2.7
Is CVE-2021-39198 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
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L |
| NVD | 3.1 | 5.4 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:L |
| NVD | 2.0 | 5.8 | AV:N/AC:M/Au:N/C:N/I:P/A:P |
| GitHub | 3.1 | 4.2 | CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:N/I:L/A:L |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | oro/crm | >=3.1.0, <4.1.17 >=4.2.0, <4.2.7 |
4.1.17 4.2.7 |
Affected products
- oroinc crm
Classification
- Weakness
-
- CWE-352 Cross-Site Request Forgery
References
-
github.com
/oroinc/crm/security/advisories/GHSA-vf7h-6246-hm43
web, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2021-39198
advisory
-
github.com
/oroinc/crm
package
Sources
- CVE List CVE-2021-39198
- GitHub Advisory GHSA-vf7h-6246-hm43
- NVD CVE-2021-39198
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.