Summary
Cross site scripting in registration template in xwiki-platform
Workarounds
There are two main ways for protecting against this vulnerability, the easiest and the best one is by applying a patch in the registerinline.vm template, the patch consists in checking the value of the xredirect field to ensure it matches the following:
<input type="hidden" name="xredirect" value="$escapetool.xml($!request.xredirect)" />
If for some reason it's not possible to patch this file, another workaround is to ensure "Prevent unregistered users from viewing pages, regardless of the page rights" is not checked in the rights and apply a better right scheme using groups and rights on spaces.
References
https://jira.xwiki.org/browse/XWIKI-19291
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
Impact
We found a possible XSS vector in the registerinline.vm template related to the xredirect hidden field.
This template is only used in the following conditions:
- the wiki must be open to registration for anyone
- the wiki must be closed to view for Guest users (more specifically the XWiki.Registration page must be forbidden in View for guest user)
A way to obtain the second condition is when administrators checked the "Prevent unregistered users from viewing pages, regardless of the page rights" box in the administration rights.
Untrusted input is rendered as active markup in a victim's browser, which can run script in their session. Typical impact: session or credential theft, and actions taken as the user.
CVE-2022-23622 has a CVSS score of 7.4 (High). The vector is network-reachable, no privileges required, and user interaction required. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (12.10.11, 13.4.7, 13.10.3); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
The issue is patched in versions 12.10.11, 14.0-rc-1, 13.4.7, 13.10.3.
Frequently Asked Questions
- What is CVE-2022-23622? CVE-2022-23622 is a high-severity cross-site scripting (XSS) vulnerability in org.xwiki.platform:xwiki-platform-web-templates (maven), affecting versions >= 2.6.1, < 12.10.11. It is fixed in 12.10.11, 13.4.7, 13.10.3. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
- How severe is CVE-2022-23622? CVE-2022-23622 has a CVSS score of 7.4 (High). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.xwiki.platform:xwiki-platform-web-templates are affected by CVE-2022-23622? org.xwiki.platform:xwiki-platform-web-templates (maven) versions >= 2.6.1, < 12.10.11 is affected.
- Is there a fix for CVE-2022-23622? Yes. CVE-2022-23622 is fixed in 12.10.11, 13.4.7, 13.10.3. Upgrade to this version or later.
- Is CVE-2022-23622 exploitable, and should I be worried? Whether CVE-2022-23622 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2022-23622 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2022-23622?
- Upgrade
org.xwiki.platform:xwiki-platform-web-templatesto 12.10.11 or later - Upgrade
org.xwiki.platform:xwiki-platform-web-templatesto 13.4.7 or later - Upgrade
org.xwiki.platform:xwiki-platform-web-templatesto 13.10.3 or later
- Upgrade