CVE-2022-2885 json
Cross-site Scripting (XSS) - Stored in yetiforcecompany/yetiforcecrm
published 4y ago modified 4mo ago also GHSA-rjvc-mf7r-ch7r , EUVD-2022-6619
- cvss
- 6.7
- version 3.0, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 42%
- public exploits
- 0
- none known
Summary
Cross-site Scripting (XSS) - Stored in GitHub repository yetiforcecompany/yetiforcecrm prior to 6.4.0.
Patch / fix
- packagist yetiforce/yetiforce-crm 6.4.0
- yetiforcecompany yetiforcecompany/yetiforcecrm 6.4.0
Is CVE-2022-2885 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.49% chance of exploitation in the next 30 days, higher than 42% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- huntr.dev https://huntr.dev/bounties/edeed309-be07-4373-b15e-2d1eb415eb89 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.0 | 6.7 | CVSS:3.0/AV:L/AC:H/PR:H/UI:N/S:C/C:H/I:L/A:L |
| NVD | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
| GitHub | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| packagist | yetiforce/yetiforce-crm | <6.4.0 |
6.4.0 |
Affected products
- yetiforcecompany yetiforcecompany/yetiforcecrm
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
References
-
github.com
/yetiforcecompany/yetiforcecrm/commit/a9ad9ee089b575855b9e5e202b4990a15811e8d2
web, patch, third-party-advisory
-
huntr.dev
/bounties/edeed309-be07-4373-b15e-2d1eb415eb89
web, exploit, patch, third-party-advisory
-
nvd.nist.gov
/vuln/detail/CVE-2022-2885
advisory
-
github.com
/yetiforcecompany/yetiforcecrm
package
Sources
- CVE List CVE-2022-2885
- GitHub Advisory GHSA-rjvc-mf7r-ch7r
- NVD CVE-2022-2885
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.