CVE-2025-32968: org.xwiki.platform:xwiki-platform-oldcore allows SQL injection in short form select requests through the script query API
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(XWSNAME, XWSVALUE) from xwikistrings #'").execute() {{/velocity}}
Patches
This has been patched in 16.10.1, 16.4.6 and 15.10.16.
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
Other sources
XWiki is a generic wiki platform. In versions starting from 1.6-milestone-1 to before 15.10.16, 16.4.6, and 16.10.1, 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. This issue has been patched in versions 16.10.1, 16.4.6 and 15.10.16. 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.
— MITRE
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2025-32968?
CVE-2025-32968 has a high severity level due to its potential for blind SQL injection, allowing attackers to execute arbitrary SQL statements.
How do I fix CVE-2025-32968?
To remediate CVE-2025-32968, upgrade to the following patched versions: 16.10.1, 16.4.6, or 15.10.16 of org.xwiki.platform:xwiki-platform-oldcore.
Which software is affected by CVE-2025-32968?
CVE-2025-32968 affects the org.xwiki.platform:xwiki-platform-oldcore package in specific versions ranging from 15.10.16 to 16.10.1.
What kind of attack does CVE-2025-32968 allow?
CVE-2025-32968 allows authenticated users with SCRIPT rights to perform blind SQL injection attacks, potentially compromising the database.
Are there any workarounds for CVE-2025-32968?
For CVE-2025-32968, the recommended solution is to upgrade to the non-vulnerable versions rather than relying on temporary workarounds.