Summary
Velocity execution without script right through tree macro
Workarounds
A possible workaround is to:
- modify the page XWiki.DocumentTreeMacros
- search for the code
#set ($discard = $translatedDocument.setTitle($translatedDocument.title)) - modify it into
#set ($discard = $translatedDocument.setcomment(''))
References
- https://jira.xwiki.org/browse/XWIKI-20625
- https://github.com/xwiki/xwiki-platform/commit/41d7dca2d30084966ca6a7ee537f39ee8354a7e3
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
Impact
It's possible to execute a Velocity script without script right through the document tree.
To reproduce:
- As a user without script right, create a document, e.g., named Nasty Title
- Set the document's title to
$request.requestURI - Click "Save & View"
- Reload the page in the browser
The navigation panel displays a document named with the current URL, showing that the Velocity code has been executed even though the user doesn't have script right.
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-50732 has a CVSS score of 8.3 (High). The vector is network-reachable, no 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.7, 15.2-rc-1); 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
This has been patched in XWiki 14.10.7 and 15.2RC1.
Frequently Asked Questions
- What is CVE-2023-50732? CVE-2023-50732 is a high-severity incorrect authorization vulnerability in org.xwiki.platform:xwiki-platform-index-tree-macro (maven), affecting versions >= 8.3-rc-1, < 14.10.7. It is fixed in 14.10.7, 15.2-rc-1. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- How severe is CVE-2023-50732? CVE-2023-50732 has a CVSS score of 8.3 (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-index-tree-macro are affected by CVE-2023-50732? org.xwiki.platform:xwiki-platform-index-tree-macro (maven) versions >= 8.3-rc-1, < 14.10.7 is affected.
- Is there a fix for CVE-2023-50732? Yes. CVE-2023-50732 is fixed in 14.10.7, 15.2-rc-1. Upgrade to this version or later.
- Is CVE-2023-50732 exploitable, and should I be worried? Whether CVE-2023-50732 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-2023-50732 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-2023-50732?
- Upgrade
org.xwiki.platform:xwiki-platform-index-tree-macroto 14.10.7 or later - Upgrade
org.xwiki.platform:xwiki-platform-index-tree-macroto 15.2-rc-1 or later
- Upgrade