Summary
XWiki vulnerable to click-jacking through CSS injection in comments
Workarounds
There's no out-of-the-box workaround, but it should be possible to partly reuse the javascript code provided for the security measure in a JSX object inside the wiki, to request the same kind of confirmation.
References
- JIRA ticket: https://jira.xwiki.org/browse/XWIKI-23433
- Documentation of the new security measure: https://www.xwiki.org/xwiki/bin/view/ReleaseNotes/Data/XWiki/17.9.0RC1/Entry006/
- Commit for the security fix: https://github.com/xwiki/xwiki-platform/commit/29cb81f3a5387cf822d7e7534bdd63903275f86b
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira XWiki.org
- Email us at Security Mailing List
Attribution
Thanks Tomas Keech (Sentrium Security Ltd) for reporting this vulnerability.
Impact
It's possible using comments to inject CSS that would transform the full wiki in a link area leading to a malicious page. All versions of XWiki are impacted by this kind of attack.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The problem has been patched not by preventing injecting CSS in comments, which is currently a feature of XWiki, but by requiring confirmation from users when driving them to untrusted domains after clicking on a link, thus preventing any click-jacking attack.
This security measure has been put in place in XWiki 17.9.0, 17.4.6, 16.10.13.
Frequently Asked Questions
- What is CVE-2026-26000? CVE-2026-26000 is a medium-severity security vulnerability in org.xwiki.platform:xwiki-platform-web (maven), affecting versions >= 17.5.0, < 17.9.0. It is fixed in 17.9.0, 17.4.6, 16.10.13.
- Which versions of org.xwiki.platform:xwiki-platform-web are affected by CVE-2026-26000? org.xwiki.platform:xwiki-platform-web (maven) versions >= 17.5.0, < 17.9.0 is affected.
- Is there a fix for CVE-2026-26000? Yes. CVE-2026-26000 is fixed in 17.9.0, 17.4.6, 16.10.13. Upgrade to this version or later.
- Is CVE-2026-26000 exploitable, and should I be worried? Whether CVE-2026-26000 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-26000 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-26000?
- Upgrade
org.xwiki.platform:xwiki-platform-webto 17.9.0 or later - Upgrade
org.xwiki.platform:xwiki-platform-webto 17.4.6 or later - Upgrade
org.xwiki.platform:xwiki-platform-webto 16.10.13 or later
- Upgrade