CVE-2025-24893: XWiki Platform allows remote code execution as guest via SolrSearchMacros request
9.8
CVSS Score
3.1
Basic Information
CVE ID
GHSA ID
EPSS Score
0.99733%
CWE
Published
2/20/2025
Updated
2/20/2025
KEV Status
No
Technology
Java
Technical Details
CVSS Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Package Name | Ecosystem | Vulnerable Versions | First Patched Version |
---|---|---|---|
org.xwiki.platform:xwiki-platform-search-solr-ui | maven | >= 5.3-milestone-2, < 15.10.11 | 15.10.11 |
org.xwiki.platform:xwiki-platform-search-solr-ui | maven | >= 16.0.0-rc-1, < 16.4.1 | 16.4.1 |
Vulnerability Intelligence
Miggo AI
Root Cause Analysis
The vulnerability allows remote code execution via a crafted 'text' parameter in a request to Main/SolrSearch
when media=rss
. The core issue lies in how the RSS feed content, which includes this user input, is rendered.
The commit 67021db9b8ed26c2236a653269302a86bf01ef40
patches this by modifying Main/SolrSearchMacros.xml
.
- The
outputRSSFeed
macro withinMain.SolrSearchMacros.xml
was directly outputting the feed content using$xwiki.feed.getFeedOutput($feed, 'rss_2.0')
. This direct output allowed the XWiki rendering engine to process any embedded scripts (like Groovy macros) within the feed content that originated from the user's 'text' parameter. This is where the vulnerability (unsafe rendering sink) was located. The patch changes this to use a new#rawResponse
macro, which explicitly sets the content type and writes the data raw, crucially calling$xcontext.setFinished(true)
to prevent further rendering and script execution. - The
handleSolrSearchRequest
macro, also inMain.SolrSearchMacros.xml
, is responsible for handling the incoming request. It takes therequest.text
(user input) and uses it to create the feed via$services.search.solr.createFeed(...)
. This feed is then passed tooutputRSSFeed
. Therefore,handleSolrSearchRequest
is the function that processes the potentially malicious input and directs it to the vulnerable rendering logic inoutputRSSFeed
.
Both macros are identified: outputRSSFeed
for containing the vulnerable rendering code and handleSolrSearchRequest
for processing the malicious input and calling the vulnerable rendering part. The names provided are the Velocity macro names, which are the most precise identifiers in this context.