Summary
Workarounds
We're not aware of any workarounds except for being careful whom you grant script right.
Attribution
We thank Youssef Azefzaf for discovering and reporting this vulnerability.
Impact
An improperly protected scripting API allows any user with script right to bypass the sandboxing of the Velocity scripting API and execute, e.g., arbitrary Python scripts, allowing full access to the XWiki instance and thereby compromising the confidentiality, integrity and availability of the whole instance. Note that script right already constitutes a high level of access that we don't recommend giving to untrusted users.
The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.
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.
Remediation advice
The vulnerability has been patched in XWiki 17.4.8 and 17.10.1 by requiring programming right to access the affected scripting API.
Frequently Asked Questions
- What is CVE-2026-33229? CVE-2026-33229 is a high-severity missing authorization vulnerability in org.xwiki.platform:xwiki-platform-oldcore (maven), affecting versions >= 17.0.0-rc-1, < 17.4.8. It is fixed in 17.4.8, 17.10.1. The application does not perform an authorization check before performing a sensitive operation.
- Which packages are affected by CVE-2026-33229?
org.xwiki.platform:xwiki-platform-oldcore(maven) (versions >= 17.0.0-rc-1, < 17.4.8)org.xwiki.platform:xwiki-platform-legacy-oldcore(maven) (versions >= 17.0.0-rc-1, < 17.4.8)
- Is there a fix for CVE-2026-33229? Yes. CVE-2026-33229 is fixed in 17.4.8, 17.10.1. Upgrade to this version or later.
- Is CVE-2026-33229 exploitable, and should I be worried? Whether CVE-2026-33229 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-2026-33229 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-2026-33229?
- Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 17.4.8 or later - Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 17.10.1 or later - Upgrade
org.xwiki.platform:xwiki-platform-legacy-oldcoreto 17.4.8 or later - Upgrade
org.xwiki.platform:xwiki-platform-legacy-oldcoreto 17.10.1 or later
- Upgrade