Home
» Security vulnerabilities
» CVE-2022-1681
Authentication Bypass Using an Alternate Path or Channel in GitHub repository requarks/wiki prior to 2.5.281. User can get root user permissions
NVD Status： Modified ，CVE State: published
Threat Intelligence & Risk Assessment for CVE-2022-1681
Conclusion & alert: CVE-2022-1681 is rated High Exploit Risk (61.4/100) : CVSS High severity, with medium exploitation likelihood (EPSS 0.27%).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-1681
EDB-ID
Source
Kind
Published
Link
—
nvd_ref
exploit_tag
Exploit-DB ↗
Exploit prediction scoring system (EPSS) score for CVE-2022-1681
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-05-21
0.18%
0.27%
+0.09%
2
2025-05-13
0.04%
0.18%
+0.14%
3
2025-03-30
—
0.04%
—
Full EPSS history
(7 records total)
Common vulnerability scoring system (CVSS) metrics for CVE-2022-1681
CVSS metrics for this CVE.
Base score
Version
Severity
Vector
Exploitability
Impact
Score source
7.2
3.1
HIGH
CVSS:3.1/AV:N/AC:L/PR:H/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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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.2
5.9
[email protected]
7.2
3.0
HIGH
CVSS:3.0/AV:N/AC:L/PR:H/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:H)
They need powerful rights—admin, root, or similar—before this pays off.
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.2
5.9
[email protected]
9.0
2.0
HIGH
AV:N/AC:L/Au:S/C:C/I:C/A:C
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:C)
Complete confidentiality impact.
Integrity impact (I:C)
Complete integrity impact.
Availability impact (A:C)
Complete availability impact.
8.0
10.0
[email protected]
Weakness enumeration for CVE-2022-1681
Affected software / configurations for CVE-2022-1681
Vendor
Product
Version
Raw CPE
requarks
wiki.js
< 2.5.281
cpe:2.3:a:requarks:wiki.js:*:*:*:*:*:*:*:*
References for CVE-2022-1681
cvelogic
Threat Intelligence