XWiki vulnerable to click-jacking through CSS injection in comments
CVE-2026-26000GHSA-74rh-c5rh-88vg
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.xwiki.platform:xwiki-platform-web 17.9.0, 17.4.6, 16.10.13), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Maven org.xwiki.platform:xwiki-platform-web
- Affected
- >= 17.5.0, < 17.9.0>= 17.0.0-rc-1, < 17.4.6< 16.10.13
- Fixed in
- 17.9.0, 17.4.6, 16.10.13
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-74rh-c5rh-88vg lists affected ranges: Maven org.xwiki.platform:xwiki-platform-web >=17.5.0 =17.0.0-rc-1 =0 <16.10.13
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 5.3 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N · score source
- EPSS
- CVE-2026-26000: 0.32% estimated exploitation activity in the next 30 days; percentile 24.52 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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. Patches 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. 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:…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-74rh-c5rh-88vg
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-26000 Advisory: XWiki vulnerable to click-jacking through CSS injection in comments IDs: CVE-2026-26000, GHSA-74rh-c5rh-88vg Record: https://patchnext.com/advisories/cve-2026-26000 (revision 1, source checked 26 Oct 2026, 16:44 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 5.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: org.xwiki.platform:xwiki-platform-web 17.9.0, 17.4.6, 16.10.13. A vendor fix does not mean a deployment is fixed. ## Affected components - Maven org.xwiki.platform:xwiki-platform-web: affected >= 17.5.0, < 17.9.0; >= 17.0.0-rc-1, < 17.4.6; < 16.10.13; fixed in 17.9.0, 17.4.6, 16.10.13 ## Suggested inspection (read-only) - Maven org.xwiki.platform:xwiki-platform-web: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on org.xwiki.platform:xwiki-platform-web. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-74rh-c5rh-88vg (GitHub-reviewed advisory GHSA-74rh-c5rh-88vg lists affected ranges: Maven org.xwiki.platform:xwiki-platform-web >=17.5.0 =17.0.0-rc-1 =0 <16.10.13) Commands are suggestions: review each one before running it.
Loading voting…