Home
» Security vulnerabilities
» CVE-2021-4111
yetiforcecrm is vulnerable to Business Logic Errors
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2021-4111
Conclusion & alert: CVE-2021-4111 is rated Exploit Available (50/100) : CVSS Medium severity, with low exploitation likelihood (EPSS 0.17%).Core evidence: 1 public exploit reference(s) are indexed (Exploit-DB).Mandatory action: Public exploits are available—assess exposure, apply mitigations, and prioritize patching.
Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.
Public exploit references (Exploit-DB) for CVE-2021-4111
EDB-ID
Source
Kind
Published
Link
—
nvd_ref
exploit_tag
Exploit-DB ↗
Exploit prediction scoring system (EPSS) score for CVE-2021-4111
EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).
#
Date
Old EPSS score
New EPSS score
Delta (New - Old)
1
2025-03-30
0.15%
0.17%
+0.02%
2
2025-03-29
0.15%
0.15%
-0.01%
3
2025-03-17
—
0.15%
—
Full EPSS history
(7 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2021-4111
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
4.3
3.1
MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:N)
Service keeps running; no real outage angle.
2.8
1.4
[email protected]
7.3
3.0
HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:L)
Some sensitive info could get out, but not a total data dump.
Integrity (I:L)
Attackers could change some data, but it’s limited—not everything goes.
Availability (A:L)
Might cause slowdowns, glitches, or partial disruption—not a full brick.
3.9
3.4
[email protected]
4.0
2.0
MEDIUM
AV:N/AC:L/Au:S/C:N/I:P/A:N
Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:S)
A single authentication is required.
Confidentiality impact (C:N)
No confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
8.0
2.9
[email protected]
Weakness enumeration for CVE-2021-4111
GitHub Security Advisory for CVE-2021-4111
GHSA-7v7w-f7c6-f829 · Severity: high · Ecosystem: composer
— YetiForceCRM is vulnerable to Business Logic Errors because product amount can be a negative number
Affected software / configurations for CVE-2021-4111
References for CVE-2021-4111
cvelogic
Threat Intelligence