GHSA-x2qm-r4wx-8gpg
CRITICALGHSA-x2qm-r4wx-8gpg is a critical-severity (CVSS 10) CWE-95 vulnerability in org.xwiki.platform:xwiki-platform-flamingo-theme-ui. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-x2qm-r4wx-8gpg is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
org.xwiki.platform:xwiki-platform-flamingo-theme-ui Eval Injection vulnerability
Blast Radius
org.xwiki.platform:xwiki-platform-flamingo-theme-ui☕org.xwiki.platform:xwiki-platform-flamingo-theme-ui☕org.xwiki.platform:xwiki-platform-flamingo-theme-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
It's possible to inject arbitrary wiki syntax including Groovy, Python and Velocity script macros via the newThemeName request parameter (URL parameter), in combination with additional parameters form_token=1&action=create.
For instance: http://127.0.0.1:8080/xwiki/bin/view/FlamingoThemesCode/WebHomeSheet?newThemeName=foo%22%2F%7D%7D%7B%7Basync%20async%3D%22true%22%20cached%3D%22false%22%20context%3D%22doc.reference%22%7D%7D%7B%7Bgroovy%7D%7Dprintln(%22hello%20from%20groovy!%22)%7B%7B%2Fgroovy%7D%7D%7B%7B%2Fasync%7D%7D&form_token=1&action=create will execute the following groovy code: println("hello from groovy!") on the server.
Patches
This has been patched in the supported versions 13.10.10, 14.9-rc-1, and 14.4.6.
Workarounds
It is possible to edit FlamingoThemesCode.WebHomeSheet and manually perform the changes from the patch fixing the issue.
References
- https://github.com/xwiki/xwiki-platform/commit/ea2e615f50a918802fd60b09ec87aa04bc6ea8e2#diff-e2153fa59f9d92ef67b0afbf27984bd17170921a3b558fac227160003d0dfd2aR283-R284
- https://jira.xwiki.org/browse/XWIKI-19757
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-flamingo-theme-ui | ≥ 6.2.4&&< 13.10.10 | 13.10.10 |
| ☕Maven | org.xwiki.platform:xwiki-platform-flamingo-theme-ui | ≥ 14.0&&< 14.4.6 | 14.4.6 |
| ☕Maven | org.xwiki.platform:xwiki-platform-flamingo-theme-ui | ≥ 14.5&&< 14.9-rc-1 | 14.9-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-flamingo-theme-ui. 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-flamingo-theme-ui to 13.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x2qm-r4wx-8gpg 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-x2qm-r4wx-8gpg 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-x2qm-r4wx-8gpg. 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-x2qm-r4wx-8gpg in your dependencies?
O3 detects GHSA-x2qm-r4wx-8gpg across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.