How severe is CVE-2025-32971?

CVE-2025-32971 has a CVSS score of 3.8/10, rated LOW. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2025-32971?

CVE-2025-32971 affects the following packages: org.xwiki.platform:xwiki-platform-search-solr-api (Maven), org.xwiki.platform:xwiki-platform-search-solr-api (Maven), org.xwiki.platform:xwiki-platform-search-solr-api (Maven). Ecosystems affected: Maven.

How do I fix CVE-2025-32971?

Update org.xwiki.platform:xwiki-platform-search-solr-api to 15.10.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32971 is resolved across your whole dependency graph.

How do I detect CVE-2025-32971 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-search-solr-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2025-32971 if there is no patch (or I can't update yet)?

Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Is CVE-2025-32971 actively exploited in the wild?

No public exploit code has been indexed for CVE-2025-32971 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2025-32971?

CVE-2025-32971 has an EPSS (Exploit Prediction Scoring System) score of 0.4%, placing it in the 35th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2025-32971?

CVE-2025-32971 is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2025-32971 published, and has it been updated?

CVE-2025-32971 was published on April 30, 2025 and was last updated on October 28, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕

☕ Maven

Not in CISA KEV

LOW severity

CVE-2025-32971 — xwiki-platform-search-sol…

LOWFix: xwiki/xwiki-platform@6570f40

CVE-2025-32971 is a low-severity (CVSS 3.8) CWE-863 vulnerability in org.xwiki.platform:xwiki-platform-search-solr-api. A fix is available for org.xwiki.platform:xwiki-platform-search-solr-api — see the affected versions and patch details below.

XWiki Solr script service doesn't take dropped programming right into account

Also known asGHSA-987p-r3jc-8c8v

Published

Apr 30, 2025

Updated

Oct 28, 2026

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Nov 3, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

Proof-of-concept exploit code exists

CISA’s SSVC triage found public proof-of-concept exploit code for this CVE, though no confirmed active exploitation.

Exploitation and automatability from CISA’s SSVC triage for CVE-2025-32971.

EPSS Exploitation Probability

via FIRST.org ↗

0.4%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs35th percentile — riskier than 35% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

3 pkgs affected

☕org.xwiki.platform:xwiki-platform-search-solr-api☕org.xwiki.platform:xwiki-platform-search-solr-api☕org.xwiki.platform:xwiki-platform-search-solr-api

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

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.

Patches

This has been patched in XWiki 15.10.13, 16.8.0RC1, and 16.4.4.

Workarounds

We're not aware of any workarounds apart from being careful whom you grant script right.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.xwiki.platform:xwiki-platform-search-solr-api`	≥ 4.5.1&&< 15.10.13	15.10.13`org.xwiki.platform:xwiki-platform-search-solr-api:15.10.13`
☕Maven	`org.xwiki.platform:xwiki-platform-search-solr-api`	≥ 16.0.0-rc-1&&< 16.4.4	16.4.4`org.xwiki.platform:xwiki-platform-search-solr-api:16.4.4`
☕Maven	`org.xwiki.platform:xwiki-platform-search-solr-api`	≥ 16.5.0-rc-1&&< 16.8.0-rc-1	16.8.0-rc-1`org.xwiki.platform:xwiki-platform-search-solr-api:16.8.0-rc-1`

Affected Products

1 product · 3 configurations

Application

xwikixwiki

≥ 16.5.0 && < 16.8.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.xwiki.platform:xwiki-platform-search-solr-api, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.xwiki.platform:xwiki-platform-search-solr-api to 15.10.13 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-32971 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

### 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