NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
CRITICAL severity

CVE-2022-1411 — yetiforce-crm

CRITICALFix: yetiforcecompany/yetiforcecrm@bf69c42

CVE-2022-1411 is a critical-severity (CVSS 9.1) Unrestricted File Upload vulnerability in yetiforce/yetiforce-crm. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for yetiforce/yetiforce-crm — see the affected versions and patch details below.

Unrestructed file upload in yetiforcecompany/yetiforcecrm

Also known asGHSA-pqr6-3j58-9w58
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
1 known
Exploitation data as of Nov 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.8%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk
0.00%0.42%0.84%1.26%0.3%0.8%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐘yetiforce/yetiforce-crm

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagistyetiforce/yetiforce-crmall versions6.4.0composer require yetiforce/yetiforce-crm:^6.4.0

Affected Products

1 product · 1 configurations
Application
yetiforce customer relationship managementyetiforce
< 6.4.0
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for yetiforce/yetiforce-crm, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update yetiforce/yetiforce-crm to 6.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-1411 is resolved across your whole dependency graph.

  3. Workarounds

    Treat uploaded files as untrusted until proven otherwise: validate the actual content type rather than the supplied extension, store uploads outside the web root on a volume mounted without execute permission, and rename them to server-generated identifiers so an attacker cannot choose the path a request will later resolve.

Frequently Asked Questions

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.
O3 Security · Impact-Aware SCA

Is CVE-2022-1411 in your dependencies?

Find it across Packagist, including transitive dependencies.

CVE-2022-1411: yetiforce-crm — Fixed in 6.4.0