Unrestructed file upload in yetiforcecompany/yetiforcecrm

published 2022-05-05 4 y ago modified 2026-06-17 4 mo ago also GHSA-pqr6-3j58-9w58 , EUVD-2022-4809

cvss: 9.1; version 3.0, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.8%; EPSS 0.8% chance of exploitation in 30 days, percentile 55%
public exploits: 0; none known

Unrestructed file upload in GitHub repository yetiforcecompany/yetiforcecrm prior to 6.4.0. Attacker can send malicious files to the victims is able to retrieve the stored data from the web application without that data being made safe to render in the browser and steals victim's cookie leads to account takeover.

Patch / fix

fixed in 2 links 1

packagist yetiforce/yetiforce-crm 6.4.0
yetiforcecompany yetiforcecompany/yetiforcecrm 6.4.0

github.com/yetiforcecompany/yetiforcecrm@bf69c42 commit

Exploit prediction

0.76% chance of exploitation in the next 30 days, higher than 55% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

huntr.dev https://huntr.dev/bounties/75c7cf09-d118-4f91-9686-22b142772529 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.0	9.1	CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:H
NVD	3.1	6.1	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
NVD	2.0	4.3	AV:N/AC:M/Au:N/C:N/I:P/A:N
GitHub	3.1	6.1	CVSS:3.1/AV:N/AC:L/PR:N/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-434 Unrestricted Upload of File with Dangerous Type

References

github.com /yetiforcecompany/yetiforcecrm/commit/bf69c427260011ffca42f7b6935bb54080c54124
web, patch, third-party-advisory
huntr.dev /bounties/75c7cf09-d118-4f91-9686-22b142772529
web, exploit, third-party-advisory
nvd.nist.gov /vuln/detail/CVE-2022-1411
advisory
github.com /yetiforcecompany/yetiforcecrm
package

Sources

CVE List CVE-2022-1411
GitHub Advisory GHSA-pqr6-3j58-9w58
NVD CVE-2022-1411

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.

Summary