Summary
Solr script service doesn't take dropped programming right into account
Workarounds
We're not aware of any workarounds apart from being careful whom you grant script right.
Impact
The Solr script service that is accessible in XWiki's scripting API normally requires programming right to be called. Due to using the wrong API for checking rights, it doesn't take the fact into account that programming rights might have been dropped by calling $xcontext.dropPermissions(). If some code relies on this for the safety of executing Velocity code with the wrong author context, this could allow a user with script right to either cause a high load by indexing documents or to temporarily remove documents from the search index. We're not aware that this is exploitable in XWiki itself.
To reproduce, a user with programming right can add the following XWiki syntax to a page:
{{velocity}}
$xcontext.dropPermissions()
$services.solr.index('document:xwiki:Main.WebHome')
{{/velocity}}
This should trigger an error in XWiki's log, otherwise the installation is vulnerable.
The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions. Typical impact: unauthorized data access or execution of privileged operations.
CVE-2025-32971 has a CVSS score of 3.8 (Low). The vector is network-reachable, high privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (15.10.13, 16.4.4, 16.8.0-rc-1); upgrading removes the vulnerable code path.
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 XWiki 15.10.13, 16.8.0RC1, and 16.4.4.
Frequently Asked Questions
- What is CVE-2025-32971? CVE-2025-32971 is a low-severity incorrect authorization vulnerability in org.xwiki.platform:xwiki-platform-search-solr-api (maven), affecting versions >= 4.5.1, < 15.10.13. It is fixed in 15.10.13, 16.4.4, 16.8.0-rc-1. The application does not correctly enforce access controls, allowing a principal to access resources or operations beyond their granted permissions.
- How severe is CVE-2025-32971? CVE-2025-32971 has a CVSS score of 3.8 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which versions of org.xwiki.platform:xwiki-platform-search-solr-api are affected by CVE-2025-32971? org.xwiki.platform:xwiki-platform-search-solr-api (maven) versions >= 4.5.1, < 15.10.13 is affected.
- Is there a fix for CVE-2025-32971? Yes. CVE-2025-32971 is fixed in 15.10.13, 16.4.4, 16.8.0-rc-1. Upgrade to this version or later.
- Is CVE-2025-32971 exploitable, and should I be worried? Whether CVE-2025-32971 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-32971 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-32971?
- Upgrade
org.xwiki.platform:xwiki-platform-search-solr-apito 15.10.13 or later - Upgrade
org.xwiki.platform:xwiki-platform-search-solr-apito 16.4.4 or later - Upgrade
org.xwiki.platform:xwiki-platform-search-solr-apito 16.8.0-rc-1 or later
- Upgrade