GHSA-9cqm-5wf7-wcj7
CRITICALXWiki Platform users may execute anything with superadmin right through comments and async macro
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-async-macro☕org.xwiki.platform:xwiki-platform-rendering-async-macro☕org.xwiki.platform:xwiki-platform-rendering-async-macroReal-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
Comments are supposed to be executed with the right of superadmin but in restricted mode (anything dangerous is disabled) but the async macro is not taking into account the restricted mode.
This means that any user with comment right can use the async macro to make it execute any wiki content with the right of superadmin as in:
{{async}} {{groovy}}println "it works !"{{/groovy}} {{/async}}
Patches
This has been patched in XWiki 14.9, 14.4.6, and 13.10.10.
Workarounds
The only known workaround consists in applying the following patch and rebuilding and redeploying org.xwiki.platform:xwiki-platform-rendering-async-macro.
References
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira
- Email us at Security ML
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-rendering-async-macro | ≥ 11.6-rc-1&&< 13.10.10 | 13.10.10 |
| ☕Maven | org.xwiki.platform:xwiki-platform-rendering-async-macro | ≥ 14.0&&< 14.4.6 | 14.4.6 |
| ☕Maven | org.xwiki.platform:xwiki-platform-rendering-async-macro | ≥ 14.5&&< 14.9 | 14.9 |
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-rendering-async-macro. 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-async-macro to 13.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-9cqm-5wf7-wcj7 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-9cqm-5wf7-wcj7 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-9cqm-5wf7-wcj7. 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-9cqm-5wf7-wcj7 in your dependencies?
O3 detects GHSA-9cqm-5wf7-wcj7 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.