Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
Maven

CVE-2026-33229

CVE-2026-33229 is a CWE-862 vulnerability in org.xwiki.platform:xwiki-platform-oldcore. O3 Security confirms whether CVE-2026-33229 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

XWiki Platform affected by remote code execution with script right through unprotected Velocity scripting API

Also known asGHSA-h259-74h5-4rh9
Published
Apr 8, 2026
Updated
Jul 27, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed

Blast Radius

4 pkgs affected
org.xwiki.platform:xwiki-platform-oldcoreorg.xwiki.platform:xwiki-platform-oldcoreorg.xwiki.platform:xwiki-platform-legacy-oldcoreorg.xwiki.platform:xwiki-platform-legacy-oldcore

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Prior to 17.4.8 and 17.10.1, 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. This vulnerability is fixed in 17.4.8 and 17.10.1.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
Mavenorg.xwiki.platform:xwiki-platform-oldcore17.0.0-rc-1&&< 17.4.817.4.8
Mavenorg.xwiki.platform:xwiki-platform-oldcore17.5.0-rc-1&&< 17.10.117.10.1
Mavenorg.xwiki.platform:xwiki-platform-legacy-oldcore17.0.0-rc-1&&< 17.4.817.4.8
Mavenorg.xwiki.platform:xwiki-platform-legacy-oldcore17.5.0-rc-1&&< 17.10.117.10.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-oldcore. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update org.xwiki.platform:xwiki-platform-oldcore to 17.4.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-33229 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2026-33229 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2026-33229. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

XWiki Platform is a generic wiki platform offering runtime services for applications built on top of it. Prior to 17.4.8 and 17.10.1, 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. This vulnerability is fixed in 17.4.8
O3 Security · Impact-Aware SCA

Is CVE-2026-33229 in your dependencies?

O3 detects CVE-2026-33229 across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.