GHSA-gpq5-7p34-vqx5
CRITICALXWiki Platform's async and display macro allow displaying and interacting with any document in restricted mode
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-oldcore☕org.xwiki.platform:xwiki-platform-oldcore☕org.xwiki.platform:xwiki-platform-oldcore☕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
It's possible to display any page you cannot access through the combination of the async and display macro.
Steps to reproduce:
- Enable comments for guests by giving guests comment rights
- As a guest, create a comment with content
{{async}}{{display reference="Menu.WebHome" /}}{{/async}} - Open the comments viewer from the menu (appends ?viewer=comments to the URL)
-> the Menu.WebHome is displayed while the expectation would be to have an error that the current user is not allowed to see it
Patches
The vulnerability has been patched in XWiki 15.0-rc-1, 14.10.3, 14.4.8, and 13.10.11.
Workarounds
There is no known workaround.
References
https://jira.xwiki.org/browse/XWIKI-20394 https://jira.xwiki.org/browse/XRENDERING-694
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-oldcore | ≥ 10.11.1&&< 13.10.11 | 13.10.11 |
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 14.0-rc-1&&< 14.4.8 | 14.4.8 |
| ☕Maven | org.xwiki.platform:xwiki-platform-oldcore | ≥ 14.5&&< 14.10.3 | 14.10.3 |
| ☕Maven | org.xwiki.platform:xwiki-platform-rendering-async-macro | ≥ 10.11.1&&< 13.10.11 | 13.10.11 |
| ☕Maven | org.xwiki.platform:xwiki-platform-rendering-async-macro | ≥ 14.0-rc-1&&< 14.4.8 | 14.4.8 |
| ☕Maven | org.xwiki.platform:xwiki-platform-rendering-async-macro | ≥ 14.5&&< 14.10.3 | 14.10.3 |
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-oldcore. 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-oldcore to 13.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-gpq5-7p34-vqx5 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-gpq5-7p34-vqx5 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-gpq5-7p34-vqx5. 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-gpq5-7p34-vqx5 in your dependencies?
O3 detects GHSA-gpq5-7p34-vqx5 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.