dbcve.org
XwikiApplication

CVE-2025-32429

CRITICAL · 9.8 CVSS v3.1 Published 2025-07-24
Fix available
A fix is available. Upgrade to 16.10.6 or later.
See remediation →
100/100
Remediation priority · Urgent
High EPSS 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. In versions 9.4-rc-1 through 16.10.5 and 17.0.0-rc-1 through 17.2.2, it's possible for anyone to inject SQL using the parameter sort of the getdeleteddocuments.vm. It's injected as is as an ORDER BY value. This is fixed in versions 16.10.6 and 17.3.0-rc-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

SQL injection vulnerability in XWiki Platform allows unauthenticated attackers to inject arbitrary SQL via the 'sort' parameter in the getdeleteddocuments.vm template. The parameter value is directly concatenated into an ORDER BY clause without sanitization, enabling complete database compromise.

MitigationUpgrade to XWiki Platform version 16.10.6 or 17.3.0-rc-1 or later. If immediate patching is not feasible, temporarily restrict access to the affected getdeleteddocuments.vm endpoint.

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:>= 9.4, < 16.10.6>= 17.0.0, <= 17.2.2

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. Check installed XWiki version
    Access the Admin Dashboard (as admin) and navigate to Info > Version, or check the version through the XWiki JAR file in the webapp directory, or query the xwikidb version table if accessible
    Affected if The installed version is >= 9.4 AND < 16.10.6, OR >= 17.0.0 AND <= 17.2.2
  2. Verify getdeleteddocuments.vm template exists
    Locate the getdeleteddocuments.vm file in the XWiki webapp directory, typically under webapps/xwiki/templates/ or within the WAR file
    Affected if The template file exists in the installation
  3. Confirm endpoint accessibility
    Attempt to access the affected URL endpoint: /xwiki/bin/view/RecycleBin/delete/getdeleteddocuments.vm or /bin/view/RecycleBin/delete/getdeleteddocuments.vm (the exact path depends on XWiki configuration)
    Affected if The endpoint is reachable without authentication (unauthenticated access confirms exposure)
  4. Check for SQL injection behavior
    Send a crafted request to the affected endpoint with a 'sort' parameter containing SQL injection payload (e.g., sort=1' OR '1'='1), then observe database errors or unexpected sorting behavior in the response
    Affected if The application returns database errors or behaves unexpectedly based on injected SQL input

A user is affected if their XWiki installation version falls within 9.4 to 16.10.5 or 17.0.0 to 17.2.2 AND the getdeleteddocuments.vm template is accessible, particularly without authentication.

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 16.10.6 or later
Fixed in 16.10.6
Vendor patch github.com →
Interim mitigation

Upgrade to XWiki Platform version 16.10.6 or 17.3.0-rc-1 or later. If immediate patching is not feasible, temporarily restrict access to the affected getdeleteddocuments.vm endpoint.

Recommended fix High confidence

16.10.6 (for 16.x line) or 17.3.0-rc-1 (for 17.x line)

  1. Backup your XWiki database and installation before upgrading
  2. Identify your current XWiki version (check the about page or version file)
  3. If running 16.x (9.4-rc-1 through 16.10.5): upgrade to version 16.10.6
  4. If running 17.x (17.0.0-rc-1 through 17.2.2): upgrade to version 17.3.0-rc-1
  5. Download the appropriate upgrade package from the official XWiki downloads page (https://www.xwiki.org/xwiki/bin/view/Download/)
  6. Follow the standard XWiki upgrade procedure for your deployment method
  7. Restart the XWiki application server after the upgrade
  8. Verify the upgrade was successful by checking the version and that the getdeleteddocuments.vm template works correctly
Caveat Minor upgrade within same major branch typically has minimal breaking changes; review release notes for any specific migration notes

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

Fix this in Xwiki Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-32429 — 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-2025-32429 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