CVE-2022-29252 is a high-severity (CVSS 7.4) vulnerability in org.xwiki.platform:xwiki-platform-wiki-ui-mainwiki. A fix is available for org.xwiki.platform:xwiki-platform-wiki-ui-mainwiki — see the affected versions and patch details below.
Cross-site Scripting in XWiki Platform Wiki UI Main Wiki
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
CVE-2022-29252 plotted by exploitation likelihood (EPSS) against impact (CVSS). The shaded corner — EPSS 50%+ and CVSS 7.0+ — is where this CVE doesn't sit, though severity or exploitability alone can still warrant action.
Where this sits among everything scored
Of 379,145 CVEs with a current EPSS score, this one falls in the < 10% 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-wiki-ui-mainwiki☕org.xwiki.platform:xwiki-platform-wiki-ui-mainwiki☕org.xwiki.platform:xwiki-platform-wiki-ui-mainwikiReal-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
We found a possible XSS vector in the WikiManager.JoinWiki wiki page related to the "requestJoin" field.
Patches
The issue is patched in versions 12.10.11, 14.0-rc-1, 13.4.7, 13.10.3.
Workarounds
The easiest workaround is to edit the wiki page WikiManager.JoinWiki (with wiki editor) and change the line
<input type='hidden' name='requestJoin' value="$!request.requestJoin"/>
into
<input type='hidden' name='requestJoin' value="$escapetool.xml($!request.requestJoin)">
References
- https://jira.xwiki.org/browse/XWIKI-19292
- https://github.com/xwiki/xwiki-platform/commit/27f839133d41877e538d35fa88274b50a1c00b9b
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira XWiki
- Email us at security mailing list
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.xwiki.platform:xwiki-platform-wiki-ui-mainwiki | all versions | 12.10.11org.xwiki.platform:xwiki-platform-wiki-ui-mainwiki:12.10.11 |
| ☕Maven | org.xwiki.platform:xwiki-platform-wiki-ui-mainwiki | ≥ 13.0.0&&< 13.4.7 | 13.4.7org.xwiki.platform:xwiki-platform-wiki-ui-mainwiki:13.4.7 |
| ☕Maven | org.xwiki.platform:xwiki-platform-wiki-ui-mainwiki | ≥ 13.5.0&&< 13.10.3 | 13.10.3org.xwiki.platform:xwiki-platform-wiki-ui-mainwiki:13.10.3 |
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-wiki-ui-mainwiki, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-wiki-ui-mainwiki to 12.10.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-29252 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 CVE-2022-29252 can be triaged on real exposure rather than presence alone.
Tailored to CVE-2022-29252. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-29252 in your dependencies?
O3 Security finds CVE-2022-29252 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.