CVE-2024-41947

Workarounds

We're not aware of any workaround except upgrading.

References

• https://jira.xwiki.org/browse/XWIKI-21626
• https://github.com/xwiki/xwiki-platform/commit/821d43ec45e67d45a6735a0717b9b77fffc1cd9f

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

By creating a conflict when another user with more rights is currently editing a page, it is possible to execute JavaScript snippets on the side of the other user, which compromises the confidentiality, integrity and availability of the whole XWiki installation.

To reproduce on a XWiki instance, a user with admin rights needs to edit a document without saving right away.
Then, as another user without any other right than edit on the specific document, change the whole content to <script>alert('XSS')</script>.
When the admin user then saves the document, a conflict popup appears. If they select "Fix each conflict individually" and see an alert displaying "XSS", then the instance is vulnerable.

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-2024-41947 has a CVSS score of 9.0 (Critical). The vector is network-reachable, low 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 (15.10.8, 16.3.0-rc-1); upgrading removes the vulnerable code path.

Kodem intelligence

This has been patched in XWiki 15.10.8 and 16.3.0RC1.

1. What is CVE-2024-41947? CVE-2024-41947 is a critical-severity cross-site scripting (XSS) vulnerability in org.xwiki.platform:xwiki-platform-web-templates (maven), affecting versions >= 11.8-rc-1, < 15.10.8. It is fixed in 15.10.8, 16.3.0-rc-1. Untrusted input is rendered as active markup in a victim's browser, which can run script in their session.
2. How severe is CVE-2024-41947? CVE-2024-41947 has a CVSS score of 9.0 (Critical). 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-2024-41947? org.xwiki.platform:xwiki-platform-web-templates (maven) versions >= 11.8-rc-1, < 15.10.8 is affected.
4. Is there a fix for CVE-2024-41947? Yes. CVE-2024-41947 is fixed in 15.10.8, 16.3.0-rc-1. Upgrade to this version or later.
5. Is CVE-2024-41947 exploitable, and should I be worried? Whether CVE-2024-41947 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-2024-41947 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-2024-41947?
   • Upgrade org.xwiki.platform:xwiki-platform-web-templates to 15.10.8 or later
   • Upgrade org.xwiki.platform:xwiki-platform-web-templates to 16.3.0-rc-1 or later