CVE-2023-32069

Privilege escalation (PR)/RCE from account through class sheet

Workarounds

There are no known workarounds for it.

References

https://jira.xwiki.org/browse/XWIKI-20566
https://github.com/xwiki/xwiki-platform/commit/de72760d4a3e1e9be64a10660a0c19e9534e2ec4

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

It's possible for a user to execute anything with the right of the author of the XWiki.ClassSheet document.

Steps to Reproduce:

1. Edit your user profile with the object editor and add an object of type DocumentSheetBinding with value Default Class Sheet
2. Edit your user profile with the wiki editor and add the syntax {{async}}{{groovy}}println("Hello " + "from groovy!"){{/groovy}}{{/async}}
3. Click "Save & View"

Expected result:

An error is displayed as the user doesn't have the right to execute the Groovy macro.

Actual result:

The text "Hello from groovy!" is displayed at the top of the document.

The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.

CVE-2023-32069 has a CVSS score of 9.9 (Critical). The vector is network-reachable, low privileges required, and no user interaction. 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 (14.10.4); upgrading removes the vulnerable code path.

Kodem intelligence

Already deployed Kodem?

This has been patched in XWiki 15.0-rc-1 and 14.10.4.

1. What is CVE-2023-32069? CVE-2023-32069 is a critical-severity incorrect authorization vulnerability in org.xwiki.platform:xwiki-platform-test-ui (maven), affecting versions >= 3.3-milestone-3, < 14.10.4. It is fixed in 14.10.4. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
2. How severe is CVE-2023-32069? CVE-2023-32069 has a CVSS score of 9.9 (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-test-ui are affected by CVE-2023-32069? org.xwiki.platform:xwiki-platform-test-ui (maven) versions >= 3.3-milestone-3, < 14.10.4 is affected.
4. Is there a fix for CVE-2023-32069? Yes. CVE-2023-32069 is fixed in 14.10.4. Upgrade to this version or later.
5. Is CVE-2023-32069 exploitable, and should I be worried? Whether CVE-2023-32069 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-2023-32069 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-2023-32069? Upgrade org.xwiki.platform:xwiki-platform-test-ui to 14.10.4 or later.