GHSA-6vgh-9r3c-2cxp
HIGHImproper Neutralization of Script-Related HTML Tags (XSS) in the LiveTable 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-flamingo-skin-resources☕org.xwiki.platform:xwiki-platform-flamingo-skin☕org.xwiki.platform:xwiki-platform-flamingo☕org.xwiki.platform:xwiki-platform-web-templates☕org.xwiki.platform:xwiki-platform-web☕org.xwiki.platform:xwiki-web-standard☕org.xwiki.platform:xwiki-platform-flamingo-skin-resources☕org.xwiki.platform:xwiki-platform-flamingo-skin+10 moreReal-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
The Livetable Macro wasn't properly sanitizing column names, thus allowing the insertion of raw HTML code including JavaScript. This vulnerability was also exploitable via the Documents Macro that is included since XWiki 3.5M1 and doesn't require script rights, this can be demonstrated with the syntax {{documents id="example" count="5" actions="false" columns="doc.title, before<script>alert(1)</script>after"/}}. Therefore, this can also be exploited by users without script right and in comments. With the interaction of a user with more rights, this could be used to execute arbitrary actions in the wiki, including privilege escalation, remote code execution, information disclosure, modifying or deleting content.
Patches
This has been patched in XWiki 14.9, 14.4.6, and 13.10.10.
Workarounds
It is possible to apply the patch to existing installations without upgrading. Only the files skins/flamingo/macros.vm and templates/macros.vm in the web application directory need to be replaced by a patched version.
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-skin-resources | ≥ 1.9-milestone-2&&< 13.10.10 | 13.10.10 |
| ☕Maven | org.xwiki.platform:xwiki-platform-flamingo-skin | ≥ 1.9-milestone-2&&< 13.10.10 | 13.10.10 |
| ☕Maven | org.xwiki.platform:xwiki-platform-flamingo | ≥ 1.9-milestone-2&&< 13.10.10 | 13.10.10 |
| ☕Maven | org.xwiki.platform:xwiki-platform-web-templates | ≥ 1.9-milestone-2&&< 13.10.10 | 13.10.10 |
| ☕Maven | org.xwiki.platform:xwiki-platform-web | ≥ 1.9-milestone-2&&< 13.10.10 | 13.10.10 |
| ☕Maven | org.xwiki.platform:xwiki-web-standard | ≥ 1.9-milestone-2&&< 13.10.10 | 13.10.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-skin-resources. 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-skin-resources to 13.10.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6vgh-9r3c-2cxp 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-6vgh-9r3c-2cxp 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-6vgh-9r3c-2cxp. 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-6vgh-9r3c-2cxp in your dependencies?
O3 detects GHSA-6vgh-9r3c-2cxp across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.