{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2026-120697 in the wild and no public exploit code.","exposure":"An affected version is exposed as installed. No special setting or call is needed.","fix":"No fix has been published for CVE-2026-120697 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-120697 is a high-severity cross-site scripting vulnerability in requarks wiki, published on 16 Nov 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2026-120697 and fix it if it is affected.\n\nWhat it is: CVE-2026-120697 is a high-severity cross-site scripting vulnerability in requarks wiki, published on 16 Nov 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2026-120697 in the wild and no public exploit code.\nExposure: An affected version is exposed as installed. No special setting or call is needed.\n\nAffected product: requarks wiki. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-120697/ (Markdown: https://insights.sbomify.com/CVE-2026-120697/index.md)","id":"CVE-2026-120697","markdown":"https://insights.sbomify.com/CVE-2026-120697/index.md","name":"CVE-2026-120697","record":{"aliases":["GHSA-98c8-px3r-68c6"],"analysis":{"component_type":"web_application","exploitable_when_present":false,"fix_type":"upgrade","impacts":["data_read","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Node.js wiki","requires_auth":"low_privilege","requires_specific_call":false,"summary":"Users with page write access can store JavaScript in page slots that runs for any viewer, including privileged users, in Wiki.js.","user_interaction":"required","vuln_class":"xss","vulnerable_functions":[]},"analysis_generated_by":"sbomify/insights-2b-fp8","assigner":"GitHub_M","cpe":[],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":false,"headline":"Wiki.js: Stored XSS via Vue Slot Directives in Page Content","id":"CVE-2026-120697","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":3,"n_vendor_status":0,"next":{"headline":"Wiki.js: Root Administrator Takeover, TFA Bypass and Lock out.","id":"CVE-2026-120698"},"nickname":null,"packages":[],"prev":{"headline":"Uncontrolled Recursion in HDF5 H5B__iterate_helper() via Crafted File","id":"CVE-2026-120689"},"products":["wiki"],"published":"2026-11-16","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":null,"exploitation":null,"technical_impact":null},"state":"PUBLISHED","updated":"2026-11-16","vendor_status":[],"vendors":["requarks"]},"summary":"Users with page write access can store JavaScript in page slots that runs for any viewer, including privileged users, in Wiki.js.","url":"https://insights.sbomify.com/CVE-2026-120697/"}