Summary
XWiki Platform vulnerable to SQL injection through getdeleteddocuments.vm template sort parameter
Workarounds
There is no known workaround, other than upgrading XWiki.
References
https://jira.xwiki.org/browse/XWIKI-23093
For more information
If you have any questions or comments about this advisory:
- Open an issue in Jira XWiki.org
- Email us at Security Mailing List
Attribution
The vulnerability was identifier by Aleksey Solovev from Positive Technologies.
Impact
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.
One can see the result of the injection with http://127.0.0.1:8080/xwiki/rest/liveData/sources/liveTable/entries?sourceParams.template=getdeleteddocuments.vm&sort=injected (this example does not work, but it shows that an HQL query was executed with the passed value which look nothing like an order by value, without any kind of sanitation).
Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access. Typical impact: data disclosure or modification.
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.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
This has been patched in 17.3.0-rc-1, 16.10.6.
Frequently Asked Questions
- What is CVE-2025-32429? CVE-2025-32429 is a critical-severity SQL injection vulnerability in org.xwiki.platform:xwiki-platform-distribution-war (maven), affecting versions >= 9.4-rc-1, < 16.10.6. It is fixed in 16.10.6, 17.3.0-rc-1. Untrusted input alters a database query, allowing the attacker to read or modify data the query was not intended to access.
- Which versions of org.xwiki.platform:xwiki-platform-distribution-war are affected by CVE-2025-32429? org.xwiki.platform:xwiki-platform-distribution-war (maven) versions >= 9.4-rc-1, < 16.10.6 is affected.
- Is there a fix for CVE-2025-32429? Yes. CVE-2025-32429 is fixed in 16.10.6, 17.3.0-rc-1. Upgrade to this version or later.
- Is CVE-2025-32429 exploitable, and should I be worried? Whether CVE-2025-32429 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-2025-32429 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-2025-32429?
- Upgrade
org.xwiki.platform:xwiki-platform-distribution-warto 16.10.6 or later - Upgrade
org.xwiki.platform:xwiki-platform-distribution-warto 17.3.0-rc-1 or later
- Upgrade