XWiki does not require right warnings for notification displayer objectsGHSA-j7p2-87q3-44w7
Fix: xwiki/xwiki-platform@55c5d56GHSA-j7p2-87q3-44w7 is a CWE-357 vulnerability in org.xwiki.platform:xwiki-platform-notifications-notifiers-default. A fix is available for org.xwiki.platform:xwiki-platform-notifications-notifiers-default — see the affected versions and patch details below.
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-j7p2-87q3-44w7.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
Real-World Exposure
org.xwiki.platform:xwiki-platform-notifications-notifiers-default☕org.xwiki.platform:xwiki-platform-notifications-notifiers-default☕org.xwiki.platform:xwiki-platform-notifications-notifiers-defaultReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
Impact
When a user without script right creates a document with an XWiki.Notifications.Code.NotificationDisplayerClass object, and later an admin edits and saves that document, the possibly malicious content of that object is output as raw HTML, allowing XSS attacks. While the notification displayer executes Velocity, the existing generic analyzer already warns admins before editing Velocity code. Note that warnings before editing documents with dangerous properties have only been introduced in XWiki 15.9, before that version, this was a known issue and the advice was simply to be careful.
Patches
This vulnerability has been patched in XWiki 15.10.16, 16.4.7, and 16.10.2 by adding a required rights analyzer that warns the admin before editing about the possibly malicious code.
Workarounds
We're not aware of any real workarounds apart from just being careful with editing documents previously edited by untrusted users as a user with script, admin or programming right.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-notifications-notifiers-default | ≥ 15.9-rc-1&&< 15.10.16 | 15.10.16org.xwiki.platform:xwiki-platform-notifications-notifiers-default:15.10.16 |
| ☕Maven | org.xwiki.platform:xwiki-platform-notifications-notifiers-default | ≥ 16.0.0-rc-1&&< 16.4.7 | 16.4.7org.xwiki.platform:xwiki-platform-notifications-notifiers-default:16.4.7 |
| ☕Maven | org.xwiki.platform:xwiki-platform-notifications-notifiers-default | ≥ 16.5.0-rc-1&&< 16.10.2 | 16.10.2org.xwiki.platform:xwiki-platform-notifications-notifiers-default:16.10.2 |
Affected Products
xwikixwikiDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-notifications-notifiers-default, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-notifications-notifiers-default to 15.10.16 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-j7p2-87q3-44w7 is resolved across your whole dependency graph.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.
Frequently Asked Questions
Is GHSA-j7p2-87q3-44w7 in your dependencies?
Find it across Maven, including transitive dependencies.