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

CVE-2021-4117 — yetiforce-crm

MEDIUMFix: yetiforcecompany/yetiforcecrm@8dccd93

CVE-2021-4117 is a medium-severity (CVSS 4.3) CWE-840 vulnerability in yetiforce/yetiforce-crm. 1 public exploit reference exists, so weaponization risk is real. No vendor fix is recorded yet; mitigation options are listed below.

YetiForceCRM is vulnerable to Business Logic Errors in the weight of a product

Also known asGHSA-cxg7-84wp-8pcq
Published
Updated
Affected
1 pkg
Patched
See advisory
Exploits
1 known
Exploitation data as of Oct 10, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.7%probability of exploitation in next 30 days
Lower Risk+0.02%
Lower risk than most CVEs53th percentile — riskier than 53% of all scored CVEsHighest risk
0.00%0.41%0.82%1.23%0.2%0.7%Apr 26Aug 26Oct 26

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

How urgent is this, really

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

Where this sits among everything scored

Of 385,987 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 Business Logic Errors in the Weight of a Product since that value can be a negative number.

Affected Packages

1 total
EcosystemPackageVulnerable rangeFix
🐘Packagistyetiforce/yetiforce-crmall versionsNo fix

Affected Products

1 product · 1 configurations
Application
yetiforce customer relationship managementyetiforce
≤ 6.3.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.

yetiforcecrm is vulnerable to Business Logic Errors

huntr.devNVDDec 2021

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. Remediation status

    No patched version of yetiforce/yetiforce-crm has shipped for CVE-2021-4117 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

  3. Mitigate without a patch

    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 Business Logic Errors in the Weight of a Product since that value can be a negative number.
O3 Security · Impact-Aware SCA

Is CVE-2021-4117 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2021-4117: yetiforce-crm (Medium 4.3)