CVE-2022-36095

XWiki Cross-Site Request Forgery (CSRF) for actions on tags

Workarounds

It's possible to fix the issue without upgrading by locally modifying the documentTags.vm template in your filesystem, to apply the changes exposed there: https://github.com/xwiki/xwiki-platform/commit/7ca56e40cf79a468cea54d3480b6b403f259f9ae.

References

https://jira.xwiki.org/browse/XWIKI-19550

For more information

If you have any questions or comments about this advisory:

• Open an issue in Jira XWiki
• Email us at security ML

It's possible to perform a CSRF attack for adding or removing tags on XWiki pages.

A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones. Typical impact: state-changing actions performed as the victim without their consent.

CVE-2022-36095 has a CVSS score of 4.3 (Medium). 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 (13.10.5, 14.3); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

The problem has been patched in XWiki 13.10.5 and 14.3.

1. What is CVE-2022-36095? CVE-2022-36095 is a medium-severity cross-site request forgery (CSRF) vulnerability in org.xwiki.platform:xwiki-platform-web-templates (maven), affecting versions >= 2.0-milestone-1, < 13.10.5. It is fixed in 13.10.5, 14.3. A victim's authenticated browser session is used to submit forged requests to an application that cannot distinguish them from legitimate ones.
2. How severe is CVE-2022-36095? CVE-2022-36095 has a CVSS score of 4.3 (Medium). 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.
3. Which versions of org.xwiki.platform:xwiki-platform-web-templates are affected by CVE-2022-36095? org.xwiki.platform:xwiki-platform-web-templates (maven) versions >= 2.0-milestone-1, < 13.10.5 is affected.
4. Is there a fix for CVE-2022-36095? Yes. CVE-2022-36095 is fixed in 13.10.5, 14.3. Upgrade to this version or later.
5. Is CVE-2022-36095 exploitable, and should I be worried? Whether CVE-2022-36095 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
6. What actually determines whether CVE-2022-36095 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.
7. How do I fix CVE-2022-36095?
   • Upgrade org.xwiki.platform:xwiki-platform-web-templates to 13.10.5 or later
   • Upgrade org.xwiki.platform:xwiki-platform-web-templates to 14.3 or later

Other vulnerabilities in org.xwiki.platform:xwiki-platform-web-templates