GHSA-c32m-27pj-4xcj
XWiki's required right warnings for macros are incomplete
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-rendering-xwiki☕org.xwiki.platform:xwiki-platform-rendering-xwiki☕org.xwiki.platform:xwiki-platform-rendering-xwiki☕org.xwiki.platform:xwiki-platform-rendering-macro-cache☕org.xwiki.platform:xwiki-platform-rendering-macro-cache☕org.xwiki.platform:xwiki-platform-rendering-macro-cache☕org.xwiki.platform:xwiki-platform-security-requiredrights-default☕org.xwiki.platform:xwiki-platform-security-requiredrights-default+4 moreReal-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 editing content that contains "dangerous" macros like malicious script macros that were authored by a user with fewer rights, XWiki warns about the execution of these macros since XWiki 15.9RC1. These required rights analyzers that trigger these warnings are incomplete, allowing an attacker to hide malicious content. For most macros, the existing analyzers don't consider non-lowercase parameters. Further, most macro parameters that can contain XWiki syntax like titles of information boxes weren't analyzed at all. Similarly, the "source" parameters of the content and context macro weren't anylzed even though they could contain arbitrary XWiki syntax. In the worst case, this could allow a malicious to add malicious script macros including Groovy or Python macros to a page that are then executed after another user with programming righs edits the page, thus allowing remote code execution.
Patches
The required rights analyzers have been made more robust and extended to cover those cases in XWiki 16.4.7, 16.10.3 and 17.0.0.
Workarounds
We're not aware of any workarounds except for being careful when editing content authored by untrusted users.
References
- https://jira.xwiki.org/browse/XWIKI-22763
- https://jira.xwiki.org/browse/XWIKI-22759
- https://jira.xwiki.org/browse/XWIKI-22758
- https://jira.xwiki.org/browse/XWIKI-22799
- https://github.com/xwiki/xwiki-platform/commit/abdcefc0db27035b67329add836fd683e0cf92b8
- https://github.com/xwiki/xwiki-platform/commit/cc74dc802efe0e2d3fa2ba3355dbadc51c5fd8c7
- https://github.com/xwiki/xwiki-platform/commit/0a705e8e253cb871b804e25c53b2bde879c886bd
- https://github.com/xwiki/xwiki-platform/commit/3d451e957fe2b14459e9ac64172b4a0e4c46971c
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-rendering-xwiki | ≥ 15.9-rc-1&&< 16.4.7 | 16.4.7 |
| ☕Maven | org.xwiki.platform:xwiki-platform-rendering-xwiki | ≥ 16.5.0-rc-1&&< 16.10.3 | 16.10.3 |
| ☕Maven | org.xwiki.platform:xwiki-platform-rendering-xwiki | ≥ 17.0.0-rc-1&&< 17.0.0 | 17.0.0 |
| ☕Maven | org.xwiki.platform:xwiki-platform-rendering-macro-cache | ≥ 15.9-rc-1&&< 16.4.7 | 16.4.7 |
| ☕Maven | org.xwiki.platform:xwiki-platform-rendering-macro-cache | ≥ 16.5.0-rc-1&&< 16.10.3 | 16.10.3 |
| ☕Maven | org.xwiki.platform:xwiki-platform-rendering-macro-cache | ≥ 17.0.0-rc-1&&< 17.0.0 | 17.0.0 |
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-rendering-xwiki. 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-rendering-xwiki to 16.4.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-c32m-27pj-4xcj 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-c32m-27pj-4xcj 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-c32m-27pj-4xcj. 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-c32m-27pj-4xcj in your dependencies?
O3 detects GHSA-c32m-27pj-4xcj across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.