Home
» Security vulnerabilities
» CVE-2022-2650
Improper Restriction of Excessive Authentication Attempts in GitHub repository wger-project/wger prior to 2.2.
NVD Status: Modified ,CVE State: published
Threat Intelligence & Risk Assessment for CVE-2022-2650
Conclusion & alert: CVE-2022-2650 is rated High Exploit Risk (66.9/100) : CVSS Critical severity, with low exploitation likelihood (EPSS 0.15%). 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-2022-2650
EDB-ID
Source
Kind
Published
Link
—
nvd_ref
exploit_tag
Exploit-DB ↗
Exploit prediction scoring system (EPSS) score for CVE-2022-2650
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-08-19
0.11%
0.15%
+0.04%
2
2025-03-30
0.36%
0.11%
-0.24%
3
2025-03-29
—
0.36%
—
Full EPSS history
(8 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2022-2650
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
9.8
3.1
CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
3.9
5.9
[email protected]
7.8
3.0
HIGH
CVSS:3.0/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Click to expand
Attack vector (AV:L)
They already need access on the box, or another person has to do something wrong; it’s not a remote drive-by.
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:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
1.8
5.9
[email protected]
Weakness enumeration for CVE-2022-2650
GitHub Security Advisory for CVE-2022-2650
GHSA-gr58-76rp-mmg4 · Severity: critical · Ecosystem: pip
— wger vulnerable to brute force attempts
Affected software / configurations for CVE-2022-2650
Vendor
Product
Version
Raw CPE
wger
wger
< 2.2
cpe:2.3:a:wger:wger:*:*:*:*:*:*:*:*
References for CVE-2022-2650
cvelogic
Threat Intelligence