Summary
org.xwiki.platform:xwiki-platform-oldcore allows SQL injection in short form select requests through the script query API
Workarounds
There is no known workaround, other than upgrading XWiki.
The protection added to this REST API is the same as the one used to validate complete select queries, making it more consistent. However, while the script API always had this protection for complete queries, it's important to note that it's a very strict protection and some valid, but complex, queries might suddenly require the author to have programming right.
References
https://jira.xwiki.org/browse/XWIKI-22718
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
Impact
It is possible for a user with SCRIPT right to escape from the HQL execution context and perform a blind SQL injection to execute arbitrary SQL statements on the database backend.
Depending on the used database backend, the attacker may be able to not only obtain confidential information such as password hashes from the database, but also execute UPDATE/INSERT/DELETE queries.
The vulnerability may be tested in a default installation of XWIki Standard Flavor, including using the official Docker containers.
For example, with a MySQL or MariaDB database, you can use the following script (which a user having SCRIPT right but not PROGRAMMING right) to get the content of the xwikistrings table (which contain all the short string fields stored in objects, including passwords):
{{velocity}}
$services.query.hql("where 1<>'1\'' union select concat(XWS_NAME, XWS_VALUE) from xwikistrings #'").execute()
{{/velocity}}
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 16.10.1, 16.4.6 and 15.10.16.
Frequently Asked Questions
- What is CVE-2025-32968? CVE-2025-32968 is a high-severity SQL injection vulnerability in org.xwiki.platform:xwiki-platform-oldcore (maven), affecting versions >= 1.6-milestone-1, < 15.10.16. It is fixed in 15.10.16, 16.4.6, 16.10.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-oldcore are affected by CVE-2025-32968? org.xwiki.platform:xwiki-platform-oldcore (maven) versions >= 1.6-milestone-1, < 15.10.16 is affected.
- Is there a fix for CVE-2025-32968? Yes. CVE-2025-32968 is fixed in 15.10.16, 16.4.6, 16.10.1. Upgrade to this version or later.
- Is CVE-2025-32968 exploitable, and should I be worried? Whether CVE-2025-32968 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-32968 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-32968?
- Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 15.10.16 or later - Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 16.4.6 or later - Upgrade
org.xwiki.platform:xwiki-platform-oldcoreto 16.10.1 or later
- Upgrade