Home
» Security vulnerabilities
» CVE-2022-1235
Weak secrethash can be brute-forced in GitHub repository livehelperchat/livehelperchat prior to 3.96.
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2022-1235
Conclusion & alert: CVE-2022-1235 is rated Exploit Available (57.9/100) : CVSS High severity, with low exploitation likelihood (EPSS 0.12%).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-1235
EDB-ID
Source
Kind
Published
Link
—
nvd_ref
exploit_tag
Exploit-DB ↗
Exploit prediction scoring system (EPSS) score for CVE-2022-1235
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-04-12
0.03%
0.12%
+0.09%
2
2025-03-17
0.05%
0.03%
-0.02%
3
2023-03-07
—
0.05%
—
Full EPSS history
(4 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2022-1235
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
8.2
3.1
HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/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: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:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
3.9
4.2
[email protected]
7.5
3.0
HIGH
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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: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:N)
Doesn’t really leak secrets in a meaningful way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
3.9
3.6
[email protected]
6.4
2.0
MEDIUM
AV:N/AC:L/Au:N/C:P/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:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:N)
No availability impact.
10.0
4.9
[email protected]
Weakness enumeration for CVE-2022-1235
GitHub Security Advisory for CVE-2022-1235
GHSA-vx8v-g3p3-88vg · Severity: high · Ecosystem: composer
— Weak password hash in LiveHelperChat
Affected software / configurations for CVE-2022-1235
References for CVE-2022-1235
cvelogic
Threat Intelligence