<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sat, 10 Oct 2026 08:20:48 +0000</lastBuildDate>
    <item>
      <title>CVE-2025-32971 — XWiki Solr script service doesn't take dropped programming right into account</title>
      <link>https://cve.radiocsirt.org/vuln/cve-2025-32971</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; xwiki-platform&lt;/p&gt;
&lt;p&gt;XWiki is a generic wiki platform. In versions starting from 4.5.1 to before 15.10.13, from 16.0.0-rc-1 to before 16.4.4, and from 16.5.0-rc-1 to before 16.8.0-rc-1, the Solr script service doesn&amp;#39;t take dropped programming rights into account. The Solr script service that is accessible in XWiki&amp;#39;s scripting API normally requires programming rights to be called. Due to using the wrong API for checking rights, it doesn&amp;#39;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 rights to either cause a high load by indexing documents or to temporarily remove documents from the search index. This issue has been patched in versions 15.10.13, 16.4.4, and 16.8.0-rc-1.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; xwiki-platform&lt;/p&gt;
&lt;p&gt;XWiki is a generic wiki platform. In versions starting from 4.5.1 to before 15.10.13, from 16.0.0-rc-1 to before 16.4.4, and from 16.5.0-rc-1 to before 16.8.0-rc-1, the Solr script service doesn&amp;#39;t take dropped programming rights into account. The Solr script service that is accessible in XWiki&amp;#39;s scripting API normally requires programming rights to be called. Due to using the wrong API for checking rights, it doesn&amp;#39;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 rights to either cause a high load by indexing documents or to temporarily remove documents from the search index. This issue has been patched in versions 15.10.13, 16.4.4, and 16.8.0-rc-1.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cve-2025-32971</guid>
    </item>
    <item>
      <title>GHSA-987p-r3jc-8c8v — Solr script service doesn't take dropped programming right into account</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-987p-r3jc-8c8v</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.xwiki.platform:xwiki-platform-search-solr-api&lt;/p&gt;
&lt;p&gt;### Impact
The Solr script service that is accessible in XWiki&amp;#39;s scripting API normally requires programming right to be called. Due to using the wrong API for checking rights, it doesn&amp;#39;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&amp;#39;re not aware that this is exploitable in XWiki itself.&lt;/p&gt;
&lt;p&gt;To reproduce, a user with programming right can add the following XWiki syntax to a page:
```
{{velocity}}
$xcontext.dropPermissions()
$services.solr.index(&amp;#39;document:xwiki:Main.WebHome&amp;#39;)
{{/velocity}} 
```&lt;/p&gt;
&lt;p&gt;This should trigger an error in XWiki&amp;#39;s log, otherwise the installation is vulnerable.&lt;/p&gt;
&lt;p&gt;### Patches
This has been patched in XWiki 15.10.13, 16.8.0RC1, and 16.4.4.&lt;/p&gt;
&lt;p&gt;### Workarounds
We&amp;#39;re not aware of any workarounds apart from being careful whom you grant script right.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Maven: org.xwiki.platform:xwiki-platform-search-solr-api&lt;/p&gt;
&lt;p&gt;### Impact
The Solr script service that is accessible in XWiki&amp;#39;s scripting API normally requires programming right to be called. Due to using the wrong API for checking rights, it doesn&amp;#39;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&amp;#39;re not aware that this is exploitable in XWiki itself.&lt;/p&gt;
&lt;p&gt;To reproduce, a user with programming right can add the following XWiki syntax to a page:
```
{{velocity}}
$xcontext.dropPermissions()
$services.solr.index(&amp;#39;document:xwiki:Main.WebHome&amp;#39;)
{{/velocity}} 
```&lt;/p&gt;
&lt;p&gt;This should trigger an error in XWiki&amp;#39;s log, otherwise the installation is vulnerable.&lt;/p&gt;
&lt;p&gt;### Patches
This has been patched in XWiki 15.10.13, 16.8.0RC1, and 16.4.4.&lt;/p&gt;
&lt;p&gt;### Workarounds
We&amp;#39;re not aware of any workarounds apart from being careful whom you grant script right.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-987p-r3jc-8c8v</guid>
    </item>
  </channel>
</rss>
