CVE
wiki stored XSS via Vue slot directives in page content
Affects Wiki.js 2.5.314 and earlier, where accounts with write:pages on a path can inject scripts via Vue slot directives in page content. No vendor rating is given. 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:R/S:C/C:H/I:H/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 2.5.315
- Who is exposed
- Specific setups only
Do first: Check whether your setup matches what the bug needs. Wiki.js version 2.5.314 or earlier (fixed in 2.5.315). Attacker needs an authenticated account with write:pages permission on the affected path.
- 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? →
- 17/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
Summary
Wiki.js from requarks lets a logged-in user who can write pages save content that runs JavaScript in the browser of anyone who views that page. The script can read data from the viewer's session, alter what is displayed, show phishing content, or carry out actions as the viewer, including privileged actions if an administrator opens the page. An attacker can do this remotely with a low-privilege login, but a victim has to open the affected page.
Original description
Wiki.js is an open source wiki app built on Node.js. Prior to 2.5.315, an authenticated user with write:pages can store JavaScript expressions in the v-slot:tabs or v-slot:content attributes of page HTML because server/modules/rendering/html-security/renderer.js adds those executable Vue directives to DOMPurify's allowlist. The sanitized output is inserted as rendered page HTML and later compiled by the Vue 2 runtime compiler, so the expressions execute in the Wiki.js origin when another user views the page even when the author lacks write:scripts and administrative permissions. The script runs with the viewer's browser session and can read same-origin data, modify displayed content, present phishing content, or perform actions available to that viewer, including privileged GraphQL operations when a privileged user opens the page. This issue is fixed in version 2.5.315.
Who should check
Teams running Wiki.js 2.5.314 or earlier (requarks wiki, npm wikijs) where accounts hold write:pages, so any page viewer can be targeted.
“Wiki.js 2.5.314 allows the Vue directives v-slot:tabs and v-slot:content in sanitized page HTML.”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure8/25Specific setups only, reachable over the network
- Reach?/20Unknown. No tracked technology or package matched
- Severity8.7/10CVSS 8.7
- No patch0/5No signal
What would change the score
- Would score about 67 if added to CISA KEV
- Would score about 62 if CISA's SSVC rates exploitation active
- Would score about 24 if CISA's SSVC rates it automatable
What to do
Check whether your setup matches what the bug needs.
Wiki.js version 2.5.314 or earlier (fixed in 2.5.315). Attacker needs an authenticated account with write:pages permission on the affected path.Upgrade 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-120697 (Wiki.js: Stored XSS via Vue Slot Directives in Page Content), 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-120697 (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):
- Wiki.js version 2.5.314 or earlier (fixed in 2.5.315). (source: https://github.com/requarks/wiki/security/advisories/GHSA-98c8-px3r-68c6)
- Attacker needs an authenticated account with write:pages permission on the affected path. (source: https://github.com/requarks/wiki/security/advisories/GHSA-98c8-px3r-68c6)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, low-privilege login, a user action.
CISA KEV: CVE-2026-120697 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-120697 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-98c8-px3r-68c6
- https://github.com/requarks/wiki/commit/1161ddc6e6f4388a15d90278d55b099248ce6e79
- 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-120697
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-120697"}.Timeline
- CVE published
- First seen by cve.now
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-120697
Is CVE-2026-120697 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. No public exploit code is tracked.Source: cve.now feed data
What does this mean?
Wiki.js does not properly handle the Vue directives v-slot:tabs and v-slot:content in sanitized page HTML. Script placed through them runs in the Wiki.js origin in a viewer's browser session, so it can act as that user, read accessible data, change displayed content, or show phishing content.Source: github.com
Which versions are affected by CVE-2026-120697?
wiki: before 2.5.315.Source: cve.now feed data
Am I affected, and how do I check?
Wiki.js 2.5.314 or earlier is affected. The exposure requires an authenticated account with write:pages permission on the affected path. Check the installed Wiki.js version against 2.5.314 to see which side of the range a deployment falls on.Source: github.com
How do I fix CVE-2026-120697?
Upgrade Wiki.js to version 2.5.315 or later, which is the fixed version.Source: github.com