Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

CVE-2021-4092 — yetiforce-crm

MEDIUMFix: yetiforcecompany/yetiforcecrm@585da04

CVE-2021-4092 is a medium-severity (CVSS 4.3) Cross-Site Request Forgery (CSRF) vulnerability in yetiforce/yetiforce-crm. A fix is available for yetiforce/yetiforce-crm — see the affected versions and patch details below.

yetiforcecrm is vulnerable to Cross-Site Request Forgery (CSRF)

Also known asGHSA-v4cr-m5f8-gxw8
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.4%probability of exploitation in next 30 days
Lower Risk+0.01%
Lower risk than most CVEs32th percentile — riskier than 32% of all scored CVEsHighest risk
0.00%0.30%0.60%0.90%0.1%0.4%0.4%0.4%0.4%Jun 26Sep 26Oct 26

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

How urgent is this, really

CVE-2021-4092 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,386 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

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

yetiforcecrm is vulnerable to Cross-Site Request Forgery (CSRF)

Affected Packages

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

Affected Products

1 product · 1 configurations
Application
yetiforce customer relationship managementyetiforce
< 6.3.0
range

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.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-4092 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

yetiforcecrm is vulnerable to Cross-Site Request Forgery (CSRF)
O3 Security · Impact-Aware SCA

Is CVE-2021-4092 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2021-4092: yetiforce-crm CSRF — Fixed in 6.3.0