GHSA-9pc2-x9qf-7j2q
CRITICALorg.xwiki.platform:xwiki-platform-legacy-notification-activitymacro Eval Injection vulnerability
EPSS Exploitation Probability
EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.
Blast Radius
org.xwiki.platform:xwiki-platform-legacy-notification-activitymacro☕org.xwiki.platform:xwiki-platform-legacy-notification-activitymacro☕org.xwiki.platform:xwiki-platform-legacy-notification-activitymacroReal-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
Any user with view rights on commonly accessible documents including the legacy notification activity macro can execute arbitrary Groovy, Python or Velocity code in XWiki leading to full access to the XWiki installation. The root cause is improper escaping of the macro parameters of the legacy notification activity macro. This macro is installed by default in XWiki.
A proof of concept exploit is
{{activity wikis="~" /~}~} {{async async=~"true~" cached=~"false~" context=~"doc.reference~"~}~}{{groovy~}~}println(~"Hello from Groovy!~"){{/groovy~}~}"/}}
If the output of this macro is
The [notifications] macro is a standalone macro and it cannot be used inline. Click on this message for details.
Hello from Groovy!" displayMinorEvents="false" displayRSSLink="false" /}}
or similar, the XWiki installation is vulnerable. The vulnerability can be exploited via every wiki page that is editable including the user's profile, but also with just view rights using the HTMLConverter that is part of the CKEditor integration which is bundled with XWiki.
Patches
The vulnerability has been patched in XWiki 13.10.11, 14.4.7 and 14.10.
Workarounds
The issue can be fixed by replacing the code of the legacy notification activity macro by the patched version. Alternatively, if the macro isn't used, the document XWiki.Notifications.Code.Legacy.ActivityMacro can also be completely deleted.
References
- https://github.com/xwiki/xwiki-platform/commit/94392490884635c028199275db059a4f471e57bc
- https://jira.xwiki.org/browse/XWIKI-20258
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
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-legacy-notification-activitymacro | ≥ 10.9&&< 13.10.11 | 13.10.11 |
| ☕Maven | org.xwiki.platform:xwiki-platform-legacy-notification-activitymacro | ≥ 14.0-rc-1&&< 14.4.7 | 14.4.7 |
| ☕Maven | org.xwiki.platform:xwiki-platform-legacy-notification-activitymacro | ≥ 14.5&&< 14.10 | 14.10 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & 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-legacy-notification-activitymacro. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.xwiki.platform:xwiki-platform-legacy-notification-activitymacro to 13.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9pc2-x9qf-7j2q is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-9pc2-x9qf-7j2q is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-9pc2-x9qf-7j2q. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-9pc2-x9qf-7j2q in your dependencies?
O3 detects GHSA-9pc2-x9qf-7j2q across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.