dbcve.org
XwikiApplication

CVE-2026-33229

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-08
Fix available
A fix is available. Upgrade to 17.4.8 / 17.10.1 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

XWiki Platform prior to 17.4.8 and 17.10.1 contains an improperly protected scripting API that allows users with script right to bypass Velocity sandboxing and execute arbitrary Python scripts, achieving full compromise of the XWiki instance.

MitigationUpgrade XWiki to version 17.4.8 or 17.10.1 or later to apply the security patch that properly restricts the scripting API.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
XwikiApplication
Affected:>= 17.0.0, < 17.4.8>= 17.5.0, < 17.10.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed XWiki Platform version
    Log into XWiki as an administrator, then navigate to the Administration > About page, or check the version from the installation directory in the file xar/org/xwiki-platform-main-application/pom.xml or the application's WAR file metadata.
    Affected if The version falls within >= 17.0.0, < 17.4.8 or >= 17.5.0, < 17.10.1
  2. Verify if users have script rights
    Navigate to Administration > Rights > Users and Groups. Locate the 'Script' permission entry. Check if any user or group granted the script right is untrusted or belongs to a low-privilege account.
    Affected if Any untrusted or low-privilege user has been granted the script right permission
  3. Confirm Python scripting is enabled
    Navigate to Administration > Advanced > Python. Verify if the 'Enable Python' setting is turned on, or check the xwiki.cfg configuration file for the xwiki.render.macrolist.includePython parameter.
    Affected if Python scripting is enabled on the XWiki instance
  4. Check for suspicious Python script execution
    Review XWiki logs (typically in the logs directory or via the administration interface) for entries containing 'python' or 'PyObject' around script executions, and audit any recently created or modified pages containing {{python}}...{{/python}} macros.
    Affected if Unauthorised Python script macros are present in wiki content or log entries show Python execution outside expected workflows

A user is affected if their XWiki version is in the vulnerable range (17.0.0-17.4.7 or 17.5.0-17.10.0) AND untrusted users have script rights AND Python scripting is enabled, allowing sandbox bypass via Python execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 17.4.8 / 17.10.1 or later
Fixed in 17.4.817.10.1
Vendor patch github.com →
Interim mitigation

Upgrade XWiki to version 17.4.8 or 17.10.1 or later to apply the security patch that properly restricts the scripting API.

Recommended fix High confidence

17.4.8 (for 17.0.0-17.4.x) or 17.10.1 (for 17.5.0-17.10.x)

  1. 1. Identify the current XWiki version by checking the XWiki administration console or the version.properties file.
  2. 2. For versions >= 17.0.0 and < 17.4.8: Plan upgrade to version 17.4.8.
  3. 3. For versions >= 17.5.0 and < 17.10.1: Plan upgrade to version 17.10.1.
  4. 4. Review the XWiki upgrade guide at https://www.xwiki.org/xwiki/bin/view/Documentation/AdminGuide/Installation/
  5. 5. Create a complete backup of the XWiki database and filesystem before proceeding.
  6. 6. Stop the XWiki application server.
  7. 7. Download the appropriate XWiki WAR file for the target version (17.4.8 or 17.10.1) from https://www.xwiki.org/xwiki/bin/view/Download/
  8. 8. Replace the existing WAR file and restart the application server.
Caveat Standard XWiki upgrade considerations apply - review release notes for any configuration or feature changes between your current version and the target version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Xwiki Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-33229 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-33229 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data