GHSA-p5f8-qf24-24cj
HIGHVelocity execution without script right through tree 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-index-tree-macro☕org.xwiki.platform:xwiki-platform-index-tree-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 execute a Velocity script without script right through the document tree.
To reproduce:
- As a user without script right, create a document, e.g., named Nasty Title
- Set the document's title to
$request.requestURI - Click "Save & View"
- Reload the page in the browser
The navigation panel displays a document named with the current URL, showing that the Velocity code has been executed even though the user doesn't have script right.
Patches
This has been patched in XWiki 14.10.7 and 15.2RC1.
Workarounds
A possible workaround is to:
- modify the page XWiki.DocumentTreeMacros
- search for the code
#set ($discard = $translatedDocument.setTitle($translatedDocument.title)) - modify it into
#set ($discard = $translatedDocument.setcomment(''))
References
- https://jira.xwiki.org/browse/XWIKI-20625
- https://github.com/xwiki/xwiki-platform/commit/41d7dca2d30084966ca6a7ee537f39ee8354a7e3
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-index-tree-macro | ≥ 8.3-rc-1&&< 14.10.7 | 14.10.7 |
| ☕Maven | org.xwiki.platform:xwiki-platform-index-tree-macro | ≥ 15.0-rc-1&&< 15.2-rc-1 | 15.2-rc-1 |
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-index-tree-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-index-tree-macro to 14.10.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-p5f8-qf24-24cj 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-p5f8-qf24-24cj 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-p5f8-qf24-24cj. 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-p5f8-qf24-24cj in your dependencies?
O3 detects GHSA-p5f8-qf24-24cj across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.