CVE
wiki auth bypass in user management allows root takeover
Requires an authenticated Wiki.js account holding the manage:users permission, which can take over local administrator accounts. Fixed in 2.5.315.
Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
- Exploited
- Proof of concept public, per CISA
- Fix
- Fixed in 2.5.315
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Requires an authenticated account that holds the manage:users permission
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 33/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Specific setups only
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
- Exploitation: poc
- Automatable: no
- Technical impact: total
Summary
Wiki.js, the open source wiki app, has a flaw that lets a remote attacker who already has a low-privilege account with user-management rights change the password of any local account, including the Root administrator. They can also clear that account's two-factor authentication, lock out real administrators by stripping their group memberships, and then log in as the takeover account.
Original description
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.now Index
- Exploitation15/40CISA rates a proof of concept as public
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity9.8/10CVSS 8.8, total technical impact per CISA
- No patch0/5No signal
What would change the score
- Would score about 68 if added to CISA KEV
- Would score about 63 if CISA's SSVC rates exploitation active
- Would score about 40 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Requires an authenticated account that holds the manage:users permissionUpgrade to a fixed version: 2.5.315.
Check your systems with an agent
Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.
Check whether my systems are affected by CVE-2026-120698 (Wiki.js: Root Administrator Takeover, TFA Bypass and Lock out.), using the cve.now data below.
Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.
What cve.now has for CVE-2026-120698 (entry last updated 2026-11-16):
Affected:
- requarks wiki: fixed in 2.5.315
Fixed versions: 2.5.315.
Conditions (all must be true for the bug to be hit):
- Requires an authenticated account that holds the manage:users permission (source: https://github.com/requarks/wiki/security/advisories/GHSA-45cp-v5ph-2jhm)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, no user action.
CISA KEV: CVE-2026-120698 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120698 only. If you also check another CVE, look up its own KEV status; never assume it from this one.
How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.
Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/requarks/wiki/security/advisories/GHSA-45cp-v5ph-2jhm
- https://github.com/requarks/wiki/commit/2df962c86dfb265c2e2da4c04f935ad9f24fdffb
- https://github.com/requarks/wiki/releases/tag/v2.5.315
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.
Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.
Entry: https://cve.now/CVE-2026-120698
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-120698"}.Timeline
- CVE published
- First seen by cve.now
- CISA SSVC assessment
Exploitation: poc · Automatable: no · Technical impact: total
- Record last updated
Affected versions
- requarks wiki
fixed in 2.5.315
Evidence 5
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 2
- Repository
- Repository
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-120698
Is CVE-2026-120698 being exploited?
It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. CISA's SSVC assessment notes a proof of concept exists. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
An account holding only manage:users can change the password of local administrator accounts, remove their TFA factors, and demote all administrators. This can leave the installation without a legitimate administrator.Source: github.com
Which versions are affected by CVE-2026-120698?
wiki: before 2.5.315.Source: cve.now feed data
Am I affected, and how do I check?
Wiki.js versions before 2.5.315 are affected, and the attacker needs an authenticated account with the manage:users permission. The installed version can be checked in the Wiki.js administration area, and the accounts holding manage:users can be reviewed in the user permission settings.Source: github.com
How do I fix CVE-2026-120698?
Upgrade Wiki.js to version 2.5.315, which is the listed fixed version.Source: github.com