Wiki.js is an open source wiki app built on Node.js. Prior to 2.5.315, an authenticated account with only manage:users can use users.update to change the password of any local account, including the Root administrator and other accounts with manage:system, by omitting the optional groups argument, which is automatically allowed and bypasses destination-group authorization without checking the target's current privileges. The attacker can use users.disableTFA to clear the same target's tfaIsActive state and TFA secret without a target-privilege check, then authenticate with the replacement password. Supplying groups: [] to users.update can remove every group relationship from a selected administrator and leave the installation without a legitimate account holding manage:system. Additional administrators with IDs greater than 2 can also be deactivated or deleted. This issue is fixed in version 2.5.315.
CVE-2026-120698
This high-severity CVE scores 8.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4% (38th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.
Also known asEUVD-2026-126662 (ENISA EUVD)Source: ENISA EUVD
- CISA's Vulnrichment rates exploitation as PoC; EchelonGraph holds no exploit-code reference for it
A fix is available — apply it.
- CVSS v3
- 8.8
- EG Score
- 8.8HIGHlow confidence
- EG Risk
- 56EG Risk 56/100
EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.
How it’s computed (value × EchelonGraph’s weight)Severity88% × 45%Impact severity (EG Severity): CVSS 8.8 of 10. Never the KEV-floored or EPSS-lifted EG Score.Exploitation40% × 40%EchelonGraph's fixed weight for EG-KEV Tier 3 (Elevated): a constant, not a probability.Automatability0% × 15%CISA's SSVC Automatable value: no (Vulnrichment).SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 0.4%
- EPSS %ILE
- 38th
- KEV
- Not listed
What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)
The EG score (8.8): severity, escalated by confirmed exploitation. This CVE's 8.8 is its impact severity (EG Severity), not escalated.
- EG Severity
- 8.8 HIGHCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.a secondary CVSS source · CVSS v3.0 or v3.1
- EG Likelihood
- 0.4% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
- Confirmed exploitation
- None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
- EG Priority
- SSVC Track* at medium mission impactTrack at low, Track* at medium and Attend at high mission impact.CISA BOD 26-04: 14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source, and whom BOD 26-04 binds: the SSVC and BOD 26-04 blocks below.
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table
BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
The score's inputs: In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it
Published
November 16, 2026
Last Modified
November 16, 2026
Advisory Details (3)
Auto-updated Nov 16, 2026v2.5.315
Patch available: requarks/wiki v2.5.315
https://github.com/requarks/wiki/releases/tag/v2.5.315commit 2df962c86dfb (requarks/wiki)
Patch available: requarks/wiki v2.5.315 (contains commit 2df962c86dfb)
https://github.com/requarks/wiki/commit/2df962c86dfb265c2e2da4c04f935ad9f24fdffbRoot Administrator Takeover, TFA Bypass and Lock out. · Advisory · requarks/wiki · GitHub
https://github.com/requarks/wiki/security/advisories/GHSA-45cp-v5ph-2jhmWeakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 8× in last 7d / 8× in last 30d)
Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed its CVE.org record (CNA or CISA ADP). An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). "EchelonGraph re-scored" is our own recompute of this CVE's score, not an update from a source, and is not counted in the refreshes above. Most recent first.
- 2026-11-21 16:38 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-20 16:36 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-19 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-19 16:26 UTCOSV refresh
- 2026-11-18 16:33 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-17 16:34 UTCEPSS rescoreEPSS 0.4% · 38th percentile
- 2026-11-16 22:30 UTCEchelonGraph re-scored
- 2026-11-16 22:02 UTCENISA EUVD ID recordedEUVD-2026-126662 · Source: ENISA EUVD
- 2026-11-16 21:43 UTCEchelonGraph re-scored
- 2026-11-16 21:35 UTCEchelonGraph re-scored
- 2026-11-16 21:25 UTCEchelonGraph re-scoredFirst assessed: 8.8 HIGH
- 2026-11-16 21:23 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Frequently asked(5)
What is CVE-2026-120698?
When was the CVE record for CVE-2026-120698 published?
Is CVE-2026-120698 actively exploited?
What is the CVSS score of CVE-2026-120698?
How do I remediate CVE-2026-120698?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-120698
Is Your Infrastructure Affected by CVE-2026-120698?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.