GHSA-f4v8-58f6-mwj4 is a critical-severity (CVSS 9.9) CWE-95 vulnerability in org.xwiki.platform:xwiki-platform-flamingo-theme-ui. 1 public exploit reference exists, so weaponization risk is real. A fix is available for org.xwiki.platform:xwiki-platform-flamingo-theme-ui — see the affected versions and patch details below.
org.xwiki.platform:xwiki-platform-flamingo-theme-ui Eval Injection vulnerability
Exploitation Status
Proof-of-concept exploit code exists
- CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.
- A successful exploit gives an attacker total control of the affected component, not partial access.
Exploitation and automatability from CISA’s SSVC triage for GHSA-f4v8-58f6-mwj4.
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.
How urgent is this, really
GHSA-f4v8-58f6-mwj4 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE sits: patch-first territory.
Where this sits among everything scored
Of 378,567 CVEs with a current EPSS score, this one falls in the 50–90% band (highlighted). Real counts from FIRST.org, not a sample — log-scaled since the landscape is heavily right-skewed.
Real-World Exposure
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
Any user with view rights on commonly accessible documents can execute arbitrary Groovy, Python or Velocity code in XWiki leading to full access to the XWiki installation. The root cause is improper escaping of the documentTree macro parameters in This macro is installed by default in FlamingoThemesCode.WebHome. This page is installed by default.
Example of reproduction:
Open <xwiki_host>/xwiki/bin/view/%22%20%2F%7D%7D%20%7B%7Basync%20async%3D%22true%22%20cached%3D%22false%22%20context%3D%22doc.reference%22%7D%7D%7B%7Bgroovy%7D%7Dprintln(%22Hello%20%22%20%2B%20%22from%20groovy!%22)%7B%7B%2Fgroovy%7D%7D%7B%7B%2Fasync%7D%7D?sheet=FlamingoThemesCode.WebHome&xpage=view where <xwiki_host> is the URL of your XWiki installation.
The [documentTree] macro is a standalone macro and it cannot be used inline. Click on this message for details. Hello from groovy!.WebHome" /}}
is displayed. This shows that the Groovy macro that is passed in the URL has been executed and thus demonstrates a privilege escalation from view to programming rights.
Patches
The vulnerability has been patched in XWiki 13.10.11, 14.4.7 and 14.10.
Workarounds
The issue can be fixed by replacing the code of FlamingoThemesCode.WebHome by the patched version.
References
- https://jira.xwiki.org/browse/XWIKI-20279
- https://github.com/xwiki/xwiki-platform/commit/80d5be36f700adcd56b6c8eb3ed8b973f62ec0ae
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 | ≥ 7.2-rc-1&&< 13.10.11 | 13.10.11org.xwiki.platform:xwiki-platform-flamingo-theme-ui:13.10.11 |
| ☕Maven | org.xwiki.platform:xwiki-platform-flamingo-theme-ui | ≥ 14.0-rc-1&&< 14.4.7 | 14.4.7org.xwiki.platform:xwiki-platform-flamingo-theme-ui:14.4.7 |
| ☕Maven | org.xwiki.platform:xwiki-platform-flamingo-theme-ui | ≥ 14.5&&< 14.10 | 14.10org.xwiki.platform:xwiki-platform-flamingo-theme-ui:14.10 |
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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-flamingo-theme-ui to 13.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-f4v8-58f6-mwj4 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-f4v8-58f6-mwj4 can be triaged on real exposure rather than presence alone.
Tailored to GHSA-f4v8-58f6-mwj4. 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-f4v8-58f6-mwj4 in your dependencies?
O3 Security finds GHSA-f4v8-58f6-mwj4 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.