CVE-2023-41046: Velocity execution without script rights in Xwiki platform

Published Sep 1, 2023
·
Updated

Impact It is possible in XWiki to execute Velocity code without having script right by creating an XClass with a property of type "TextArea" and content type "VelocityCode" or "VelocityWiki". For the former, the syntax of the document needs to be set the xwiki/1.0 (this syntax doesn't need to be installed). In both cases, when adding the property to an object, the Velocity code is executed regardless of the rights of the author of the property (edit right is still required, though). In both cases, the code is executed with the correct context author so no privileged APIs can be accessed. However, Velocity still grants access to otherwise inaccessible data and APIs that could allow further privilege escalation.

At least for "VelocityCode", this behavior is most likely very old but only since XWiki 7.2, script right is a separate right, before that version all users were allowed to execute Velocity and thus this was expected and not a security issue.

Patches This has been patched in XWiki 14.10.10 and 15.4 RC1.

Workarounds There are no known workarounds.

References https://jira.xwiki.org/browse/XWIKI-20847 https://jira.xwiki.org/browse/XWIKI-20848 https://github.com/xwiki/xwiki-platform/commit/edc52579eeaab1b4514785c134044671a1ecd839

Other sources

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. It is possible in XWiki to execute Velocity code without having script right by creating an XClass with a property of type "TextArea" and content type "VelocityCode" or "VelocityWiki". For the former, the syntax of the document needs to be set the xwiki/1.0 (this syntax doesn't need to be installed). In both cases, when adding the property to an object, the Velocity code is executed regardless of the rights of the author of the property (edit right is still required, though). In both cases, the code is executed with the correct context author so no privileged APIs can be accessed. However, Velocity still grants access to otherwise inaccessible data and APIs that could allow further privilege escalation. At least for "VelocityCode", this behavior is most likely very old but only since XWiki 7.2, script right is a separate right, before that version all users were allowed to execute Velocity and thus this was expected and not a security issue. This has been patched in XWiki 14.10.10 and 15.4 RC1. Users are advised to upgrade. There are no known workarounds.

Affected Software

4 affected componentsFixes available
maven/org.xwiki.platform:xwiki-platform-oldcore>=15.0-rc-1<15.4-rc-1
15.4-rc-1
maven/org.xwiki.platform:xwiki-platform-oldcore>=7.2<14.10.10
14.10.10
XWiki xwiki>=7.2<14.10.10
XWiki xwiki>=15.0<15.4

Event History

Sep 1, 2023
CVE Published
via MITRE·07:59 PM
Data Sourced
via MITRE·07:59 PM
DescriptionSeverityWeakness
Sep 4, 2023
Advisory Published
04:36 PM

Frequently Asked Questions

1

What is CVE-2023-41046?

CVE-2023-41046 is a vulnerability in XWiki that allows the execution of Velocity code without script rights.

2

What is the impact of CVE-2023-41046?

The impact of CVE-2023-41046 is the ability to execute Velocity code without having script rights, potentially leading to remote code execution.

3

How can the CVE-2023-41046 vulnerability be exploited?

The CVE-2023-41046 vulnerability can be exploited by creating an XClass with a property of type 'TextArea' and content type 'VelocityCode' or 'VelocityWiki', with specific syntax.

4

Which software versions are affected by CVE-2023-41046?

XWiki versions 7.2 to 14.10.10, and versions 15.0-rc-1 to 15.4-rc-1 are affected by CVE-2023-41046.

5

How can I fix CVE-2023-41046?

To fix CVE-2023-41046, upgrade to XWiki version 15.4 or apply the recommended patches mentioned in the XWiki security advisory.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203