GHSA-fm68-j7ww-h9xf
CRITICALXWiki Platform vulnerable to Code Injection in icon themes
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-icon-default☕org.xwiki.platform:xwiki-platform-icon-script☕org.xwiki.platform:xwiki-platform-icon-script☕org.xwiki.platform:xwiki-platform-icon-default☕org.xwiki.platform:xwiki-platform-icon-ui☕org.xwiki.platform:xwiki-platform-icon-uiReal-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
By either creating a new or editing an existing document with an icon set, an attacker can inject XWiki syntax and Velocity code that is executed with programming rights and thus allows remote code execution. There are different attack vectors, the simplest is the Velocity code in the icon set's HTML or XWiki syntax definition. The icon picker can be used to trigger the rendering of any icon set. The XWiki syntax variant of the icon set is also used without any escaping in some documents, allowing to inject XWiki syntax including script macros into a document that might have programming right, for this the currently used icon theme needs to be edited. Further, the HTML output of the icon set is output as JSON in the icon picker and this JSON is interpreted as XWiki syntax, allowing again the injection of script macros into a document with programming right and thus allowing remote code execution. This impacts the confidentiality, integrity and availability of the whole XWiki instance.
Patches
This has been patched in XWiki 14.10.6 and 15.1. Icon themes now require script right and the code in the icon theme is executed within the context of the icon theme, preventing any rights escalation. A macro for displaying icons has been introduced to avoid injecting the raw wiki syntax of an icon set into another document.
Workarounds
There are no workarounds apart from upgrading to a version containing the fix.
References
- https://jira.xwiki.org/browse/XWIKI-20524
- https://github.com/xwiki/xwiki-platform/commit/b0cdfd893912baaa053d106a92e39fa1858843c7
- https://github.com/xwiki/xwiki-platform/commit/46b542854978e9caa687a5c2b8817b8b17877d94
- https://github.com/xwiki/xwiki-platform/commit/79418dd92ca11941b46987ef881bf50424898ff4
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-icon-default | ≥ 6.2-milestone-1&&< 14.10.6 | 14.10.6 |
| ☕Maven | org.xwiki.platform:xwiki-platform-icon-script | ≥ 6.2-milestone-1&&< 14.10.6 | 14.10.6 |
| ☕Maven | org.xwiki.platform:xwiki-platform-icon-script | ≥ 15.0-rc-1&&< 15.2-rc-1 | 15.2-rc-1 |
| ☕Maven | org.xwiki.platform:xwiki-platform-icon-default | ≥ 15.0-rc-1&&< 15.2-rc-1 | 15.2-rc-1 |
| ☕Maven | org.xwiki.platform:xwiki-platform-icon-ui | ≥ 6.2-milestone-1&&< 14.10.6 | 14.10.6 |
| ☕Maven | org.xwiki.platform:xwiki-platform-icon-ui | ≥ 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-icon-default. 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-icon-default to 14.10.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fm68-j7ww-h9xf 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-fm68-j7ww-h9xf 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-fm68-j7ww-h9xf. 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-fm68-j7ww-h9xf in your dependencies?
O3 detects GHSA-fm68-j7ww-h9xf across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.